--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> I saw that one too with some files. Some bug lurking
> around related to line numbers. You could copy the
PASM
> source file and remove empty lines and comments.
>
> leo
I didn't have a chance to play with parrot at all this
week. Tonight, I decid
Attached patch brings jit_debug_xcoff.c up to date with ICU changes.
Applied, thanks.
--
Dan
--"it's like this"---
Dan Sugalski even samurai
[EMAIL PROTECTED]
On Friday 21 May 2004 16:41, Bernhard Schmalhofer wrote:
> # New Ticket Created by Bernhard Schmalhofer
> # Please include the string: [perl #29782]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=29782 >
>
>
> Hi,
>
> th
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #29782]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29782 >
Hi,
this patch should make the 'Parrot m4' tests complete again.
The probl
Hi,
the code is now in. To use it, uncomment the #define _PARROTLIB in
src/dynext.c:23 (for load_bytecode) and
imcc/imcc.l:815 (for .include instructions)
and create the parrotlib.pbc file:
./parrot -o runtime/parrot/include/parrotlib.pbc \
runtime/parrot/library/parrotlib.imc
WARNIN
Hi,
On Thursday 20 May 2004, Leopold Toetsch wrote:
> I know that's too early to comment much WRT these changes. Could you
> please outline the goals that you want to achieve?
My goal is to replace the path handling code (imcc's include_file,
Parrot_load_bytecode and Parrot_load_lib) with bytecod
Le Thu, May 20, 2004 at 12:03:52PM -0700, le valeureux mongueur TOGoS a dit:
> Should aggregate PMCs (like PerlHash) be able to take
> PMCs as keys? I mean so that:
>
> $P0 = $P1[$P2]
>
> where $P1 is a PerlHash, would work. The way it works
> now is that it complains that you can't use a PMC a
# New Ticket Created by Will Coleda
# Please include the string: [perl #29771]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29771 >
The following inline patch removes what I think is currently a spurious warning in the
