On Monday 03 April 2006 13:29, [EMAIL PROTECTED] wrote:
> Modified: trunk/docs/pdds/clip/pdd07_codingstd.pod
> ===
>=== --- trunk/docs/pdds/clip/pdd07_codingstd.pod (original)
> @@ -760,6 +761,79 @@
> TBC ... Any contr
On Sunday 02 April 2006 21:17, Andy Lester wrote:
> Here's my first patch. Let me know if y'all see this sort of work as
> useful, or if I shouldn't bother.
Please continue.
In the next round of their scans, Coverity may add Parrot to the list of
projects.
For various annoying reasons, I can'
Author: petdance
Date: Mon Apr 3 13:29:21 2006
New Revision: 12104
Modified:
trunk/docs/pdds/clip/pdd07_codingstd.pod
Log:
Added section on const and localizing variables. Also, cleaned up some
whitespce
Modified: trunk/docs/pdds/clip/pdd07_codingstd.pod
===
On Apr 3, 2006, at 21:04, Bernhard Schmalhofer (via RT) wrote:
I propose to replace the enum value PARROT_EXEC_CORE with the two new
values : PARROT_EXEC_COMPILE_CORE and PARROT_EXEC_RUN_CORE.
This should make the code more clear and might limit the use of the
shared variable 'Parrot_exec_run'
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #38841]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38841 >
The exec runcore is about saving compiled JIT code in an object file and
gener
# New Ticket Created by Will Coleda
# Please include the string: [perl #38840]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38840 >
The following files reference '/dev/null/' directly, and should be
updated to use the
Andy Lester wrote:
I've been spending a lot of time the past 6 months (more?) doing source
code cleanup on the Perl 5 source code.
Welcome @ parrot, Andy.
I'd like to spend some time doing the same for Parrot, too. I hope that
doing the kind of maintenance I'm interested in makes things easi
