:
M S22-package-format.pod
Log Message:
---
Wave some hands about bundles
On 8/19/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Freitag, 18. August 2006 21:57 schrieb chromatic:
> Miguel de Icaza recently posted some thoughts about improving startup
time
> and memory usage of multiple Mono applications. What ideas can we steal
> and improve?
We have the basics o
Am Sonntag, 20. August 2006 00:26 schrieb C.J. Collier:
> > We have the basics of "AOT" since quite a time.
> >
> > leo
>
> Branch? Path? Url?
trunk! src/exec*.c!
leo
Am Freitag, 18. August 2006 21:57 schrieb chromatic:
> Miguel de Icaza recently posted some thoughts about improving startup time
> and memory usage of multiple Mono applications. What ideas can we steal
> and improve?
We have the basics of "AOT" since quite a time. It's termed EXEC run core in
Miguel de Icaza recently posted some thoughts about improving startup time and
memory usage of multiple Mono applications. What ideas can we steal and
improve?
http://tirania.org/blog/archive/2006/Aug-17.html
-- c
On Tue, Sep 07, 2004 at 07:39:49PM -0400, Dan Sugalski wrote:
: 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 de
On 9/7/04 6:31 PM, Gregory Keeney wrote:
> 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 th
Dan Sugalski wrote:
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
At 3:31 PM -0700 9/7/04, Gregory Keeney wrote:
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 ar
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
d_ 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! :)
and as you say all this really isn't about perl 6 the language.
Nicholas Clark
Thus, I reply to perl6-co
Nicholas Clark wrote:
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 o
. Then again, it might not.
The more I think about it, the greater the benefit there seems to be in
having a standardized way to include multi-platform C libraries in a
perl bundle. The Mac OS X bundles work this way (though no one really
uses this feature). But that can of worms is so large that â
13 matches
Mail list logo
