Nicholas Clark wrote:
But that does not eliminate the desire for a bundling mechanism - though any bundling mechanism should be able to take advantage of this.On Tue, Sep 07, 2004 at 06:07:24PM +0200, James Mastros wrote:
4. The single-file, platform dependent, machine language executable (realexe). This is a plain old executable, that does not particularly indicate it was generated by a "scripting" language. It requires no odd handing vs a normal executable for the target platform, because it /is/ a normal executable for the target platform. It may be staticly or dynamicly linked to the necessary libraries.
Which parrot can already do. (Or at least could, but I don't think that anyone's been checking on it recently)
Suppose I have resource files I wish to include in my bundle - although they _could_ be built into the executable that is not always desirable (especially if you want to be able to alter the resource files on the fly).
And so, we recreate NeXTStep App bundles. Wheee! :)
Thus, I reply to perl6-compiler. <grin />and as you say all this really isn't about perl 6 the language.
Nicholas Clark
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.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
