I've put together a draft with my ideas and design for
(re-)implementing lexicals in Parrot -- now available at
http://www.pmichaud.com/perl6/lexical.txt .
It's a first draft and might be a bit confusing in places,
but overall I think it's a far cleaner design than the
current implementation but
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #59202]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=59202
class names is now (always) a ResizableStringArray so we get a crash
instead of
On Mon Aug 04 20:49:25 2008, coke wrote:
On Mon Jun 09 16:49:46 2008, [EMAIL PROTECTED] wrote:
On Thu Sep 21 14:38:40 2006, particle wrote:
parrot's source is littered with internal_exception() calls, the
bulk
(all?) of which should be converted to real_exception() calls.
internal
# New Ticket Created by Chris Davaz
# Please include the string: [perl #59240]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=59240
I suggest we automate the publishing of everything under docs/* and
putting it under
On Monday 22 September 2008 08:28:26 Stephane Payrard wrote:
--- src/oo.c.orig 2008-09-22 16:59:06.0 +0200
+++ src/oo.c2008-09-22 17:12:36.0 +0200
@@ -603,10 +603,12 @@
static void
fail_if_type_exists(PARROT_INTERP, ARGIN(PMC *name))
{
- INTVAL type;
+
Will be better to change FixedIntegerArray to implement elements by
calling get_integer? And then use get_integer in all relevant places
in ResizableIntegerArray? Looks more clear to me to get the value with
get_integer and set it with set_integer_native.
Yes, that's definitely better.
Done
Patches to bigint, complex, float and string applied in r31370, thanks.
--
Salu2
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #59250]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=59250
The .sort method on FixedPMCArray fails with no applicable methods
when given
On Thursday 18 September 2008 06:13:30 Patrick R. Michaud (via RT) wrote:
When generating PIR output (e.g., from the compiler tools), we
often need to convert a Float value into an equivalent representation
for PIR. Unfortunately, all of the mechanisms I've looked at for
doing this lose a
On Tue, Sep 23, 2008 at 08:47:15PM -0700, chromatic wrote:
On Thursday 18 September 2008 06:13:30 Patrick R. Michaud (via RT) wrote:
When generating PIR output (e.g., from the compiler tools), we
often need to convert a Float value into an equivalent representation
for PIR. Unfortunately,
10 matches
Mail list logo
