On 8/9/06, Allison Randal <[EMAIL PROTECTED]> wrote:
Chip Salzenberg wrote:
>> pbc_merge doesn't allow multiple :load routines.
>
> That's a bug, Shirley.
Currently it's a feature. Only one :load routine is allowed per PIR
file, and pbc_merge basically just packs all the compiled code together.
Chip Salzenberg wrote:
pbc_merge doesn't allow multiple :load routines.
That's a bug, Shirley.
Currently it's a feature. Only one :load routine is allowed per PIR
file, and pbc_merge basically just packs all the compiled code together.
I could argue that maybe we should allow multiple :load
On Tue, Aug 08, 2006 at 06:19:18PM -0700, Allison Randal wrote:
> Leopold Toetsch wrote:
> >Am Montag, 17. Juli 2006 21:11 schrieb chromatic:
> >
> >>After discussing the idea with Allison, we both believe that Parrot should
> >>be able to produce a single PBC file from a command like:
> >>
> >>
Leopold Toetsch wrote:
Am Montag, 17. Juli 2006 21:11 schrieb chromatic:
After discussing the idea with Allison, we both believe that Parrot should
be able to produce a single PBC file from a command like:
parrot -o all_files.pbc file1.pir file2.pir ... filen.pir
Well, that exists al
Am Montag, 17. Juli 2006 21:11 schrieb chromatic:
>
> After discussing the idea with Allison, we both believe that Parrot should
> be able to produce a single PBC file from a command like:
>
> parrot -o all_files.pbc file1.pir file2.pir ... filen.pir
Well, that exists already and is named p
On Mon, Jul 17, 2006 at 12:11:55PM -0700, chromatic wrote:
> After discussing the idea with Allison, we both believe that Parrot should be
> able to produce a single PBC file from a command like:
>
> parrot -o all_files.pbc file1.pir file2.pir ... filen.pir
It'd probably make sense to defi
