pancake wrote:
> (...)
> Ok, after the presentations.. I have some problems for writing the patches
> because more than one bug report matches the same source file, and i have to
> wait everytime for commits before doing anything more. I understand that this
> is my problem and I should be pacient,
I have sent two PRs for pdb and I have a third one not yet commited.
http://rt.perl.org/rt3//Ticket/Display.html?id=31159
http://rt.perl.org/rt3//Ticket/Display.html?id=37287
My third patch is about http://rt.perl.org/rt3//Ticket/Display.html?id=31163
(list breakpoints).
Ok, after the presentati
hi,everyone.
I am learning parrot0.0.1 source code. But i don't know "padding" in
assemble.pl?
"$size += length($_) % $sizeof_packi; # Padding" ??? why need to pad?
who help ?
bloves
[EMAIL PROTECTED]
2004-11-25
I've been trying, with very limited success, to get things documented
and questions answered. (Nick's recent issues with parrot and PMCs
are just the newest of a long string of stuff) Since success has been
limited, and questions either get Warnocked or asked multiple times,
I figure it's time
OK, I've been playing with Parrot
and reading the mailing list for
a while. (My first post; whee!)
1)
What's with the big mess in
Parrot_readbc? Why not just
start a pbc file with something
like:
#comment
bytecode[7345]:\n
<7345 bytes of bytecode>
This way you wouldn't have to
worry about where
At 03:10 PM 9/7/2001 -0500, Brian Wheeler wrote:
>While waiting for Parrot (dammit, I took the wrong week off), I've been
>scanning the various documents and samples which have been floating
>around on the list. Is there a document describing Parrot syntax yet?
>Or is that a "will be released on
While waiting for Parrot (dammit, I took the wrong week off), I've been
scanning the various documents and samples which have been floating
around on the list. Is there a document describing Parrot syntax yet?
Or is that a "will be released on monday" thing as well?
Brian Wheeler
[EMAIL PROTECT
