Hi,
Muchly delayed reply, sorry.
Karl Forner wrote:
Just a little trick that can help. If the parrot interpreter in in
your path, you can workaround
the need to specify the aboslute path by using the env command. For
instance:
#! /usr/bin/env parrot
I used that trick to enable the use of per
Hi all,
It crossed my mind that we could do this, but I rejected it since it's
not really helpful. The #! line is generally only applicable to UNIX-y
systems. Even on those systems that do support it, the path to Parrot
won't always be the same either.
Just a little trick that can help. If
Am Samstag, 30. September 2006 20:13 schrieb chromatic:
> I believe that the Linux kernel at least supports alternate loaders
> (besides ld.so) when it knows the magic fingerprint at the start of a file.
See also /usr/src/linux/Documentation/mono.txt, which is of course just a
specific incarnatio
On Saturday 30 September 2006 10:00, Jonathan Worthington wrote:
> Finally, if you have a situation where having something that will Just
> Execute as a native binary is important, then I guess there's the exec
> runcore that will produce you an executable file.
I believe that the Linux kernel at
Ben Morrow wrote:
This is probably too late for a change like this, in which case ignore
me,
No, not too late - it's still a draft so there's time for suggestions.
but I don't suppose there's any chance that pbc files could allow an optional
#! line, so that they can be used as executables d
Quoth [EMAIL PROTECTED]:
> ++++
> | Offset | Length | Description|
> ++++
> | 0 | 8 | 0xFE 0x50
Author: jonathan
Date: Thu Sep 28 14:23:15 2006
New Revision: 14784
Modified:
trunk/docs/pdds/clip/pdd13_bytecode.pod
Log:
Add draft of the bytecode PDD. This is still missing some changes that need to
be made following discussion with Allison, but gives the big picture of what is
proposed.
