A vision for Parrot
Slaven Rezic
slaven.rezic at berlin.de
Wed Nov 6 03:13:03 EST 2002
More information about the Python-list mailing list
Wed Nov 6 03:13:03 EST 2002
- Previous message (by thread): A vision for Parrot
- Next message (by thread): A vision for Parrot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benjamin Goldberg <goldbb2 at earthlink.net> writes: > Frodo Morris wrote: > > > > Benjamin Goldberg wrote: > > > Frodo Morris wrote: [...] > > > Why not leave it running, so that any Perl/Python/Tcl/Ruby/Java/sh/ > > BASIC/whatever code can get to it immediately? > > Ignoring the problem of compiling those languages down to parrot > bytecode... > > How should the kernel detect that a parrot-bytecode file is, in fact, > parrot bytecode? > > For normal exe files, there's the execute bit and some standard headers. > For normal scripts, there's the execute bit and the #! line. At least on *BSD, /sys/kern/imgact_*.c control which executable types are allowed. There are imgact_aout.c, imgact_elf.c, imgact_gzip.c and imgact_shell.c, and maybe one could add an imgact_parrot.c? Regards, Slaven -- Slaven Rezic - slaven.rezic at berlin.de Berlin Perl Mongers - http://berliner.pm.org
- Previous message (by thread): A vision for Parrot
- Next message (by thread): A vision for Parrot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list