Dan Sugalski wrote:
Though it really ought to be on perl6-internals, since it's not really a perl thing at all, rather a parrot thing. I don't think I've the cycles to think about it for a while, though.
Sounds like I need to dig through the mail archives, RFC's, etc. and try to come up with a coherent picture of the state of Perl 6 app bundling. I suspect it is not an issue for Parrot only or perl only or Perl only, but something that all three will have to play nice about.
You've got things a bit turned around I think. Parrot's the engine. It provides the services, runs the code, handles the environment, and generally manages stuff. If you want, think of it as a combination CPU, OS, low-level debugging tools, and standard system libraries that compilers for all the languages use. Since you're likely going to want to package up bytecode, resources, library modules, and possibly multi-language source, it's Parrot's problem to make it work right, and set up a base so that everyone does it the same way.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
