# New Ticket Created by Kay-Uwe Huell
# Please include the string: [perl #43000]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43000 >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi parrot team,
here a clage cleaning p
On Thu May 17 01:49:39 2007, bernhard wrote:
>
>
> For the code coverage I suggest that you add an op like
> 'non_existent_op_used_for_testing' hardcoded in your test script. In
> this way you wouldn't depend on src/ops/*.ops.
>
bernhard++! I was able to implement your suggestion in less than
Author: larry
Date: Sat May 19 16:13:45 2007
New Revision: 14396
Modified:
doc/trunk/design/syn/S11.pod
Log:
format bug noticed by renormalist++
Modified: doc/trunk/design/syn/S11.pod
==
--- doc/trunk/design/syn/S11.
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sat, 19 May 2007 15:39:41 -0400
. . .
Can you put it in an email with a subject line beginning [PATCH] and
send it to [EMAIL PROTECTED] That's the entry point to our RT
system (per docs/submissions.pod).
kid51
But I'm not tr
Bob Rogers wrote:
This reports unknown method names when generating C code for PMCs.
WDOT? Is this the right place for it? Should it die instead of warn?
-- Bob Rogers
Can you put it in an email with a subject line beginning [PATCH] and
send it to
This reports unknown method names when generating C code for PMCs.
WDOT? Is this the right place for it? Should it die instead of warn?
-- Bob Rogers
http://rgrjr.dyndns.org/
* lib/Parrot/Pmc2c.pm:
+ Warn
Author: larry
Date: Sat May 19 09:45:24 2007
New Revision: 14395
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarify type semantics of sigil bindability, requested by dduncan++.
Modified: doc/trunk/design/syn/S02.pod
===
Author: larry
Date: Sat May 19 09:06:10 2007
New Revision: 14394
Modified:
doc/trunk/design/syn/S12.pod
Log:
"basal" was not intuitive, changed to "super"
"use optimize" is too long and not specific enough
now turn on class closing and finalization with "use oo :closed :final"
Modified: doc/
