Will Coleda wrote:
It's important to keep in mind that for the most part, at least on
unix-related operating systems, executables for a particular language will
simply be an 'ln -s' to /usr/bin/parrot (taking advantage of the $0
executable name information to set up certain configuration for the runtime
environment).
I'm curious how you envision languages registering themselves for this
special treatment?
I'm assuming that when a language module is installed, it will not only
store its libraries in a lib directory, and its executables in a bin
directory, but also a small config file in some directory like
/etc/parrot/languages/. That would give the name of the language, a few
relevant paths, and probably some meta-information like the license of
the language module.
Allison
