Frodo Morris wrote:
> 
> Daniel Pfeiffer wrote:
> > Hi,
> > Apache would essentially have a mod_parrot.  Maybe, if this can be
> > tested very hard, we'd even have a Parrot kernel module for all
> > Unices supporting that.  Then exec() could perform compiled scripts
> > right away, like machine code :-)
>
> I would have thought that a more platform-independent version of
> this would be, say, a parrotd, which sits on top of the kernel,
> intercepts calls to exec() bytecode and spawns the relevant processes.

What advantage would this have over putting a #! line in the bytecode?

Most existing *nix kernels (except some very old ones) will look at the
#!, parse out the path to an executable program, and the run it.

> I may be wrong.  This parrotd system would also help in projects like
> Beowulfs (although why you'd be using byte-compiled languages in
> parallel computing is beyond me), because you could use inetd or
> similar to spawn a parrot when data was received on a certain port.

I don't really see the point of having a parrotd, except if you want to
create something vaguely like PersistantPerl.

-- 
my $n = 2; print +(split //, 'e,4c3H r ktulrnsJ2tPaeh'
.."\n1oa! er")[map $n = ($n * 24 + 30) % 31, (42) x 26]