I am experimenting with registering my own compiler for the "regex"
language, but the usage is confusing. It seems that the intention is
that compilers will return a code object that gets invoked, at which
time it runs until it hits an C opcode. But what if I want to
return some values from the com
At 6:44 PM +0200 8/21/04, Mattia Barbon wrote:
Hello,
I think extenders should have access to at least some of the
flags in PObj_enum. Should we have a different function for
each flag (say: Parrot_PObj_set_custom_mark(INTERP, PMC, value),
Parrot_PObj_set_is_class(INTERP, PMC, value) or a single
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #31270]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31270 >
Hi,
I have been adding tests for the op 'does' in most of the PMC test files
Hello,
I think extenders should have access to at least some of the
flags in PObj_enum. Should we have a different function for
each flag (say: Parrot_PObj_set_custom_mark(INTERP, PMC, value),
Parrot_PObj_set_is_class(INTERP, PMC, value) or a single
Parrot_PObj_set_flag(INTERP, PMC, flag, value)
# New Ticket Created by Mattia Barbon
# Please include the string: [perl #31269]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31269 >
Hello,
this patch fixes some problems with previous week's patch:
it allowed loadi
# New Ticket Created by Mattia Barbon
# Please include the string: [perl #31268]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31268 >
Hello,
as promised with this patch:
pmc2c2 ... --library foo --c pmc1.pmc pmc
Hello,
crrently argument count is passed in I3. A comment in untils.c
near foldup says that:
TODO - IMCC and PDD 3 aren't yet in conformance. This uses the current
IMCC setup, but should be changed as soon as IMCC modified to the
correct calling conventions.
while pdd03 says:
.
Hm I should have run the test before I replied.
I removed the negatives.
Unfortunately the uppercased literals yield 0 instead of 42.
use Parrot::Test tests => 1;
output_is(<<'CODE', <<'OUTPUT', "integer literals");
print 0x2A
print "\n"
print 0X2A
print "\n"
# New Ticket Created by Duraid Madina
# Please include the string: [perl #31260]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31260 >
---
osname= linux
osvers= 2.4.25-dsa-itanium-smp
arch= ia64-linux-thread-multi
cc=
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 9:48 PM +0200 8/20/04, Leopold Toetsch wrote:
>>0) Parrot's nomenclature DOD vs GC is a bit misleading. The "DOD"
>>subsystem is the stop-the-world mark & sweep collector that recycles
>>object headers. The "GC" is the copying collector for variable size
Steve Fink wrote:
... For PerlHash, P0["foo";3] seems to be interpreted as an
iterator access? I hope there's some other way of indicating that.
Yep, KEY_integer_FLAG used to indicate, get me the next key and is used
by the iterator. But as your test shows its ambiguous.
We are already allowing
André Pang <[EMAIL PROTECTED]> wrote:
> On 21/08/2004, at 5:48 AM, Leopold Toetsch wrote:
>> 3) The copying collector isn't integrated yet. But that should be easy.
>> After finishing sweep and if there is some possible wastage in the
>> memory pools, these get compacted.
> I thought Parrot wasn'
12 matches
Mail list logo
