- Original Message -
From: "Dan Sugalski" <[EMAIL PROTECTED]>
> Actually, we don't. (Sez the man catching up on altogether too much
> mail) Since we're putting the COW stuff at the tail end, substrings
> of COW strings are fine. You set the bufstart to where the substring
> starts, buflen
$ make test
perl t/harness
t/op/basic..ok
t/op/bitwiseok
t/op/debuginfo..ok
t/op/hacks..ok
t/op/ifunless...ok
t/op/integerok
t/op/interp.ok
t/op/macro..ok, 1/9 subtest skipped
t/op/number.# Failed test (t/op/number.t at li
At 10:58 AM +0200 5/6/02, Peter Gibbs wrote:
>The COWing of substrings requires a major interface change:
>*** All references to the data in a STRING must use the new strstart pointer
>instead of bufstart ***
Actually, we don't. (Sez the man catching up on altogether too much
mail) Since we're p
At 8:44 PM -0700 5/6/02, Mark Kvale wrote:
>
>Hi all,
>
>One of the upcoming decisions that needs to be made is on the design
>of the Parrot regex engine. More specifically, (1) how will compiled
>regexes be represented and (2) how will strings be matched against
>compiled regexes?
As I come in l
Anyone care to take this task on? It doesn't have to be at all fancy.
In fact, all it needs to do is handle:
*) Label offset calcs
*) Explicit, fully-qualified, opcode names
*) Opcode args as either labels or numbers
So we'd only pass it:
foo: sub_i_i_ic 1, 2, 5
ge_i_ic
Okay, I'm working on redoing the vtable docs, since they're both
deficient and decaying. A question came up a while back about what to
do with P1 in an opcode such as:
add P1, P2, P3
And the answer is that opcode function looks like:
p1->vtable->assign_pmc(p1, p2->vtable->add_pm
