Dino Morelli wrote:
I'm working on more p6rules unit tests.
Having some trouble. First, understanding when :w means \s* and when it
means \s+
Also, these tests are failing when I use :: to separate the modifier
from the pattern. But they work when I do ':w blah' (separate with a
space). I'm not sur
I'm working on more p6rules unit tests.
Having some trouble. First, understanding when :w means \s* and when it
means \s+
Also, these tests are failing when I use :: to separate the modifier
from the pattern. But they work when I do ':w blah' (separate with a
space). I'm not sure which ways are
I'm working on an annotated version of the mailing list so that old
postings can be more easily researched. My very primitive implementation
is:
http://www.ajs.com/~ajs/cgi-bin/p6l-index.cgi
The input datafile is:
http://www.ajs.com/~ajs/p6l.dat
I'm using Google Groups as a back
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 04 May 2005 09:38:41 +0200
Bob Rogers wrote:
>. . . but I can't figure out why. I thought the patch below would
> help, but it appears that the value of c is itself broken somehow.
The memory handling was broken and disas
I now have a basic implementation for enumerated character classes in
the grammar engine (i.e., <[xyz]>, <-[xyz]>, <[x..z]>, and <-[x..z]>).
I didn't see it specified anywhere, but are the \d, \D, \s, \S, etc.
metacharacters still supposed to work inside of a enumerated character
class, as they
On Wed, May 11, 2005 at 06:24:38PM -0400, Aaron Sherman wrote:
: I'm confused as well. How does that play with Larry's comment:
:
:
http://groups-beta.google.com/group/perl.perl6.language/browse_frm/thread/54a1135c012b97bf/d17b4bc5ae7db058?q=list+comma&rnum=5&hl=en#d17b4bc5ae7db058
Well, that ap
On Thu, May 12, 2005 at 07:04:48AM +0800, Autrijus Tang wrote:
: Please sanity-check. :-)
Looks good to me. Though that should perhaps not be confused with sanity.
Larry
> That's a very interesting generalization. There are plenty of *other*
cases
where one wants an ordinal, or some other kind of $n-1 value. If C
(and
C, C, C) was a "subtract one" operator, you could write:
my $n = prompt "How many elems? ";
print @array[1st.
On Wed, May 11, 2005 at 11:45:12AM -0500, Jonathan Scott Duff wrote:
> We're discussing the proper semantics of (1)[0] on #perl6. Here's
> where we're at so far:
>
> 1. specialise ()[] to parse as (,)[]
> 2. scalars are singleton lists, so ()[] naturally
> 3. make (1)[0] die horribly.
(1)[0] mean
This is an addition to t/operators/hyper.t. It regression-checks for
the bug discussed on #perl6 (in a nutshell, hyper ops used to only
work on list literals, but not on array variables).
{ # regression test, ensure that hyper works on arrays
my @r1;
my @r2;
my @e1 = (2,
(reformatted to keep initialization with test)
Autrijus Tang skribis 2005-05-12 7:04 (+0800):
> my @a = (1,2,[3,4]);
> is([EMAIL PROTECTED], 3, 'Array length, nested []');
ok 1
> my $a = (1,2,[3,4]);
> is(+$a, 3, 'Array ref length, nested []');
ok 2
> my @b = [1,
On Wed, May 11, 2005 at 03:00:15PM -0600, Luke Palmer wrote:
> On 5/11/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> > In a somewhat related topic:
> >
> > pugs> (1,(2,3),4)[2]
> > 4
> >
> > Because the invocant to .[] assumes a Singular context.
>
> Right, but the *inside* of the invoc
Autrijus Tang wrote:
On Thu, May 12, 2005 at 12:37:06AM +0200, Fagyal Csongor wrote:
Damian Conway wrote:
print @array[1st..($n)th];
Sounds cool, but what about $n = 0; ?
Then it would be 0..-1, an empty range.
Yep, but I mean in general isn't it confusing that the 0th elem
On Thu, May 12, 2005 at 12:37:06AM +0200, Fagyal Csongor wrote:
> Damian Conway wrote:
>
> >print @array[1st..($n)th];
>
> Sounds cool, but what about $n = 0; ?
Then it would be 0..-1, an empty range.
/Autrijus/
pgpRRkOMafCIK.pgp
Description: PGP signature
Damian Conway wrote:
print @array[1st..($n)th];
Sounds cool, but what about $n = 0; ?
- Fagzal
On Wed, 2005-05-11 at 17:48, Matt Fowles wrote:
> On 5/11/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> > On 5/11/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> > > In a somewhat related topic:
> > >
> > > pugs> (1,(2,3),4)[2]
> > > 4
> > >
> > > Because the invocant to .[] assumes a Singul
Larry mused:
I'm wondering if it's just a cardinal/ordinal thing, and we can just
translate $7 to $<7th>. Then we don't have to guess where to insert
a .flat or :flat.
That's a very interesting generalization. There are plenty of *other* cases
where one wants an ordinal, or some other kind of $n-
Larry decreed:
Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
Huzzah!
Our old $0 (P5's $&) could be $<> instead, short for $ or some
such.
According to the new capture semantics document posted earlier this week:
A successful match returns a C object whose ...
string
On Wed, 11 May 2005, Patrick R. Michaud wrote:
>On Wed, May 11, 2005 at 06:16:27PM +0200, Uwe Voelker wrote:
>>
>> Btw. the tests in t/p6rules/*.t have 'no_plan'. Should this be changed
>> to reflect the correct number of tests? I have this patch ready, but I'm
>> too shy to post :-)
>
>Feel free
On Thu, May 12, 2005 at 05:19:11AM +0800, Autrijus Tang wrote:
: Sure (and done). Now that #1 is eliminated, the question is now
: whether a simple scalar can be treated as a small (one-element) array
: reference, much like a simple pair can be treated as a small
: (one-element) hash reference.
:
Leopold Toetsch wrote:
I have now implemented a C opcode and the one used signature for
MD5 as a JIT opcode for x86. But the speedup is much smaller: around 5%.
Thanks!
The problem with md5 code and Parrot JIT seems to be related to the
register allocator. md5 code is one big basic block of inte
All~
On 5/11/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> On 5/11/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> > In a somewhat related topic:
> >
> > pugs> (1,(2,3),4)[2]
> > 4
> >
> > Because the invocant to .[] assumes a Singular context.
>
> Right, but the *inside* of the invocant is
Thanks, both yours and Shillo's tests are applied (and implemented).
/Autrijus/
pgpi79NWrtGna.pgp
Description: PGP signature
On Wed, May 11, 2005 at 02:12:41PM -0700, Larry Wall wrote:
> On Thu, May 12, 2005 at 04:19:02AM +0800, Autrijus Tang wrote:
> : Hm? Under #2, no matter whether @foo is (1) or (1,2), the construct
> : (@foo)[0] would always means @foo.[0]. Not sure how the length of @foo
> : matters here.
>
> Te
On Thu, May 12, 2005 at 04:19:02AM +0800, Autrijus Tang wrote:
: Hm? Under #2, no matter whether @foo is (1) or (1,2), the construct
: (@foo)[0] would always means @foo.[0]. Not sure how the length of @foo
: matters here.
Tell you what, let's require P5's (...)[] to be translated to [...][],
so
Index: t/oo/class/basic.t
===
--- t/oo/class/basic.t(revision 2970)
+++ t/oo/class/basic.t(working copy)
@@ -21,6 +21,11 @@
my $foo_clone = $foo.clone();
ok($foo_clone ~~ Foo, '... smartmatch our $foo_clone to the Foo
class'
On Wed, May 11, 2005 at 03:00:15PM -0600, Luke Palmer wrote:
> On 5/11/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> > In a somewhat related topic:
> >
> > pugs> (1,(2,3),4)[2]
> > 4
> >
> > Because the invocant to .[] assumes a Singular context.
>
> Right, but the *inside* of the invoc
On 5/11/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> In a somewhat related topic:
>
> pugs> (1,(2,3),4)[2]
> 4
>
> Because the invocant to .[] assumes a Singular context.
Right, but the *inside* of the invocant is still a list, so it's in
list context. I think that line should return
In a somewhat related topic:
pugs> (1,(2,3),4)[2]
4
Because the invocant to .[] assumes a Singular context.
I'm not sure how any invocant can assume a Plural context anyway,
so this behaviour seems correct. Is it, though? :)
Thanks,
/Autrijus/
pgpQf1TyWmCFa.pgp
Description: PGP signat
Three years ago I wrote a simple Perl 5 script to convert the EBNF
specification of XML to Perl 6's rules.
Pugs supports rules now, so perhaps it can be tested. This is a complex
job (because it's a complex grammar, and of course it can never work
without much tweaking, and debugging grammars is p
On Wed, May 11, 2005 at 01:11:45PM -0700, Larry Wall wrote:
> On Wed, May 11, 2005 at 11:45:12AM -0500, Jonathan Scott Duff wrote:
> :
> : We're discussing the proper semantics of (1)[0] on #perl6. Here's
> : where we're at so far:
> :
> : 1. specialise ()[] to parse as (,)[]
> : 2. scalars are s
On Wed, May 11, 2005 at 11:45:12AM -0500, Jonathan Scott Duff wrote:
:
: We're discussing the proper semantics of (1)[0] on #perl6. Here's
: where we're at so far:
:
: 1. specialise ()[] to parse as (,)[]
: 2. scalars are singleton lists, so ()[] naturally
: 3. make (1)[0] die horribly.
:
: We a
On Wed, May 11, 2005 at 06:35:36PM +0200, Juerd wrote:
: Larry Wall skribis 2005-05-11 8:30 (-0700):
: > It's already the case that p5-to-p6 is going to have a *wonderful*
: > time translating $7 to $1[2][0]...
:
: If I remember correctly, ** recursively flattens, and so (**$/)[7-1]
: should work
On Wed, May 11, 2005 at 06:16:27PM +0200, Uwe Voelker wrote:
> Hello,
>
> I fixed a small typo in PBC_COMPAT.
>
> Btw. the tests in t/p6rules/*.t have 'no_plan'. Should this be changed
> to reflect the correct number of tests? I have this patch ready, but I'm
> too shy to post :-)
Feel free to
That seems reasonable to me. Please do.
Here it is (together with a gentle reminder at the end of the .t file :-)
But feel free to leave this line out.
Uwe
Index: t/p6rules/anchors.t
===
--- t/p6rules/anchors.t (revision 8065)
+++ t/p
# New Ticket Created by jerry gay
# Please include the string: [perl #35413]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35413 >
i'm converting many of the remaining internal_exception() calls to
real_exception() (excep
Tim wrote:
Seems like the last major thread on namespace issues, especially
inter-language issues, was around October last year and didn't reach
any firm conclusions.
What's the current status?
Pretty much the same. There is now an additional namespace
"__parrot_core", where MMD subroutines are ga
I've now changed the class attribute code, so that short attribute names
work too. The short names are stored in the same hash as the qualified
names. The hash is rebuilt in reverse MRO order so that a subclassed
short name invalidates a parent's short name. This attribute is still
available wi
> this simple patch removes a build warning in io\io_win32.c:
> io\io_win32.c(272) : warning C4550: expression evaluates to a function
> which is missing an argument list
The patch is applied.
This warning surfaces only because I had inadvertedly enabled
PARROT_NET_DEVEL in io/io_private.h in SV
chromatic schrieb:
On Wed, 2005-05-11 at 18:16 +0200, Uwe Voelker wrote:
I fixed a small typo in PBC_COMPAT.
Thanks, applied.
From reading PBC_COMPAT I gathered that PBC_COMPAT should only be
changed, when the PBC syntax has changed.
# The text in this file is also the base of the
# fi
On Wed, 2005-05-11 at 18:16 +0200, Uwe Voelker wrote:
> I fixed a small typo in PBC_COMPAT.
Thanks, applied.
> Btw. the tests in t/p6rules/*.t have 'no_plan'. Should this be changed
> to reflect the correct number of tests? I have this patch ready, but I'm
> too shy to post :-)
That seems rea
Seems like the last major thread on namespace issues, especially
inter-language issues, was around October last year and didn't reach
any firm conclusions.
What's the current status?
Tim.
> On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
> : But that's only the opinion of one(@Larry), not of $Larry.
>
> Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
> Our old $0 (P5's $&) could be $<> instead, short for $ or some
> such.
Why can't bare $/ jus
# New Ticket Created by jerry gay
# Please include the string: [perl #35412]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35412 >
this simple patch removes a build warning in io\io_win32.c:
io\io_win32.c(272) : warning C
Hello,
I fixed a small typo in PBC_COMPAT.
Btw. the tests in t/p6rules/*.t have 'no_plan'. Should this be changed
to reflect the correct number of tests? I have this patch ready, but I'm
too shy to post :-)
Bye,
Uwe
Index: PBC_COMPAT
==
On Wed, 2005-05-11 at 12:45, Jonathan Scott Duff wrote:
> We're discussing the proper semantics of (1)[0] on #perl6. Here's
> where we're at so far:
>
> 1. specialise ()[] to parse as (,)[]
> 2. scalars are singleton lists, so ()[] naturally
> 3. make (1)[0] die horribly.
It may or may not help,
My perspective from PDL is that "(1)[0][0][0]"..."[0]" should evaluate
to 1. The artificial distinction between a scalar and an array of
length 1 (in each dimension) is the source of endless hassles, and it's
a pretty simple DWIM to allow indexing of element 0 of any unused
dimension. That ma
On 5/11/05, Juerd <[EMAIL PROTECTED]> wrote:
> Jonathan Scott Duff skribis 2005-05-11 11:45 (-0500):
> > 1. specialise ()[] to parse as (,)[]
> > 2. scalars are singleton lists, so ()[] naturally
> > 3. make (1)[0] die horribly.
> > #2 implies that (1)[0][0][0][0] == 1
> > #1 means that (1)[0] == 1
On Wed, May 11, 2005 at 12:01:35PM -0500, Patrick R. Michaud wrote:
> Of course, this now begs the question -- where are things stored
> after doing ... ?
>
> rx :perl5 / (don't) (ray) (me) (for solar) /
>
> My guess is that within the rule they're $1, $2, $3, etc. as before,
Within the rule
On Wed, May 11, 2005 at 06:37:53PM +0200, Juerd wrote:
> Larry Wall skribis 2005-05-11 8:30 (-0700):
> > It's already the case that p5-to-p6 is going to have a *wonderful*
> > time translating $7 to $1[2][0]...
>
> Or maybe it just has to change "(" to "$1 := (", the second "(" to "$2
> := (", et
Jonathan Scott Duff skribis 2005-05-11 11:45 (-0500):
> 1. specialise ()[] to parse as (,)[]
> 2. scalars are singleton lists, so ()[] naturally
> 3. make (1)[0] die horribly.
> #2 implies that (1)[0][0][0][0] == 1
> #1 means that (1)[0] == 1 and (1)[0][0] is an error
#1 also means that ($aref)[0]
Jonathan Scott Duff wrote:
What does p6l think? (What does @Larry think?)
I favor #3 as syntax error.
But note $TSa == all( none(@Larry), one($p6l) ) or so :)
--
TSa (Thomas Sandlaß)
We're discussing the proper semantics of (1)[0] on #perl6. Here's
where we're at so far:
1. specialise ()[] to parse as (,)[]
2. scalars are singleton lists, so ()[] naturally
3. make (1)[0] die horribly.
We all seem to agree that #3 is least useful and probably wrong. But
there's a divide betwe
Larry Wall skribis 2005-05-11 8:30 (-0700):
> It's already the case that p5-to-p6 is going to have a *wonderful*
> time translating $7 to $1[2][0]...
Or maybe it just has to change "(" to "$1 := (", the second "(" to "$2
:= (", etc.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://co
Larry Wall skribis 2005-05-11 8:30 (-0700):
> It's already the case that p5-to-p6 is going to have a *wonderful*
> time translating $7 to $1[2][0]...
If I remember correctly, ** recursively flattens, and so (**$/)[7-1]
should work.
And otherwise a simple method can probably do the trick. I sugg
On Thu, May 12, 2005 at 12:06:57AM +0800, Autrijus Tang wrote:
> On Wed, May 11, 2005 at 08:30:42AM -0700, Larry Wall wrote:
> > On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
> > : But that's only the opinion of one(@Larry), not of $Larry.
> >
> > Let's go 0-based and make $0 =:=
H,
On Wed, May 11, 2005 at 08:30:42AM -0700, Larry Wall wrote:
On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
: But that's only the opinion of one(@Larry), not of $Larry.
Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
Our old $0 (P5's $&) could be $<> inst
all is good in r8061.
seems i had forgotton to flush during internal_exception in my working
copy, so i still had test failures. leo's applied your patch and added
the interpreter flushes as well, so i can revert my changes back to
HEAD.
thanks.
~jerry
On 5/10/05, François PERRAD <[EMAIL PROTEC
On Wed, May 11, 2005 at 08:30:42AM -0700, Larry Wall wrote:
>
> Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
As Decreed on perl6-language, henceforth PGE shall be using
$0, $1, $2, ... for subpattern captures and aliases into the
match object's array.
Thus It has been M
On Wed, May 11, 2005 at 08:30:42AM -0700, Larry Wall wrote:
> On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
> : But that's only the opinion of one(@Larry), not of $Larry.
>
> Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
> Our old $0 (P5's $&) could be $<>
On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
: But that's only the opinion of one(@Larry), not of $Larry.
Let's go 0-based and make $0 =:= $/[0] so that $/[] is all the parens.
Our old $0 (P5's $&) could be $<> instead, short for $ or some
such.
It's already the case that p5-to-
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> Uri Guttman wrote:
DC> Sure. Just as $42 is a shorthand for $/[42], so too $ is a
DC> shorthand for $/.
>> but then what about the different index bases for $42 and $/[42]? i
>> don't think that has been resolved (nor has mixing
On Wed, May 11, 2005 at 05:48:59PM +1000, Damian Conway wrote:
> Uri Guttman wrote:
>
> > DC> Sure. Just as $42 is a shorthand for $/[42], so too $ is a
> > DC> shorthand for $/.
> >
> >but then what about the different index bases for $42 and $/[42]? i
> >don't think that has been resolved (nor
On Wed, 2005-05-11 at 09:50, Luke Palmer wrote:
> Oh, just to avoid further confusion: In the baz() called under fatal,
> it will only turn undefs that were generated by "fail" calls into
> exceptions. Other sorts of undefs will be returned as ordinary
> undefs.
Ok, so let me try to get my head
Patrick R. Michaud wrote:
On Wed, May 11, 2005 at 10:17:30AM +0200, Leopold Toetsch wrote:
So the right thing for the logical functions seems to be, to just return
the left or right side according to their boolean value (or return a new
Boolean false in case of xor), i.e. you get a reference to o
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #35410]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35410 >
The attached patch modifies find_cclass and find_not_cclass
to return the length
On Wed, May 11, 2005 at 09:19:50AM +0200, Leopold Toetsch wrote:
> We should just have:
> x = getattribute o, "x"
> and the set equivalent:
> setattribute o, "x", x
I would much prefer this. I don't have much problem with
grabbing and using the offsets, but at the moment they're
really only
On Wed, May 11, 2005 at 10:17:30AM +0200, Leopold Toetsch wrote:
>
> So the right thing for the logical functions seems to be, to just return
> the left or right side according to their boolean value (or return a new
> Boolean false in case of xor), i.e. you get a reference to one of the
> PMCs
> > But it does raise an important point: the discrepancy between $42 and $/[41]
> > *is* a great opportunity for off-by-on errors. Previously, however, @Larry
> > have tossed back and forth the possibility of using $0 as the first capture
> > variable so that the indices of $/[0], $/[1], $/[2] mat
On 5/11/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> sub foo() {
> fail;
> }
>
> use fatal;
> sub bar() {
> foo(); # foo() throws exception
> }
>
> no fatal;
> sub baz() {
> foo(); # foo() returns undef
> }
>
> use fatal;
> bar(
On 5/11/05, Aaron Sherman <[EMAIL PROTECTED]> wrote:
> Given:
>
> "fail" with configurable behavior
> "no fatal" to make "fail" just warn
Juerd is right here, it doesn't warn. Instead of "die"ing, it returns
an undef with some helpful diagnostic information (an "unthrown
exceptio
Jerry Gay <[EMAIL PROTECTED]> wrote:
> the new *_config$(O) files are not cleaned up during make
> clean/realclean... until now. 'svn status' reports these files have
> been removed after 'make clean'
Thanks, applied.
leo
FranÃois PERRAD (via RT) wrote:
After building different revision of Parrot without 'make clean',
Just don't do that in the same directory.
The following patch (quick & dirty) delete all .pbc after linking parrot.
Not the best idea. Think: Dan's big subs, which compile for 6 hours. And
the funtio
Aaron Sherman skribis 2005-05-11 7:44 (-0400):
> "no fatal" to make "fail" just warn
I thought it wouldn't warn, but instead silently return undef (an
unthrown exception).
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.
Given:
"fail" with configurable behavior
"no fatal" to make "fail" just warn
"use fatal" to make "fail" throw exceptions
A question came up on #perl6 for the following code:
no fatal;
class Foo {
use fatal;
method bar() { fa
On Tue, May 10, 2005 at 10:22:35PM +0200, Jens Rieks wrote:
> On Tuesday 10 May 2005 20:29, Patrick R. Michaud wrote:
> > This is *excellent*.
> >
> > However, now that I look at things, I'm wondering if a slight
> > change to the specification would be in order -- in my original
> > post I said th
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35405]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35405 >
This transaction appears to have no content
After building different revision of Par
On Wed, May 11, 2005 at 09:19:50AM +0200, Leopold Toetsch wrote:
> 2) named access
>
> x = getattribute o, "Point\0x"
>
> This needs a full qualified attribute name "Class" ~ NUL ~ "Attribute".
> That's unusable for at least Python and probably more HLLs as the
> compiler has to know in which c
On Tue, May 10, 2005 at 01:13:48PM -0400, Jeff Horwitz wrote:
> as part of both the pugs and mod_parrot effort, i've started working on
> bringing the embedding and extending interfaces into the modern parrot
> era. i'd like to start by adding public APIs (Parrot_*) where necessary
> and adding mi
On Wed, 2005-05-11 at 17:48 +1000, Damian Conway wrote:
> But it does raise an important point: the discrepancy between $42 and $/[41]
> *is* a great opportunity for off-by-on errors. Previously, however, @Larry
> have tossed back and forth the possibility of using $0 as the first capture
> var
The logical MMD functions currently try to set a passed in destination
PMCs value via assign, or they return a clone of themselves.
This is verly likely wrong: not all PMCs have to implement assign:
: That's why the destination controls assignment.
Additionaly we can't assign to singletons or r/o
Damian Conway wrote:
I think this error--unintentional, I swear!--argues strongly that
internal consistency within Perl 6 is more important than historical
consistency with Perl 5's $1, $2, $3...
But that's only the opinion of one(@Larry), not of $Larry.
My opinion as none(@Larry), too. And corr
Jens Rieks wrote:
IMO, we should deprecate the old find_* ops.
It's a lot of (more or less) duplicate code, and not easy to maintain.
Yep, as well as the old is_foo opcodes and interfaces.
jens
leo
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> +++ trunk/compilers/pge/PGE/Hs.pirTue May 10 07:10:43 2005
That's the synopsis:
>@@ -8,7 +8,7 @@
> load_bytecode "PGE.pbc"
why don't you here just the same?
> .sub "__onload" @LOAD
> +.local pmc load
> +load = find_global "PG
On Wednesday 11 May 2005 04:30, Patrick R. Michaud wrote:
> ...well, in looking at it some more it's reasonable until I see
> that returning -1 is the way the other find_* ops work. So,
> part of me thinks we should either be consistent with those, or
> make the others consistent with the interpre
Uri Guttman wrote:
DC> Sure. Just as $42 is a shorthand for $/[42], so too $ is a
DC> shorthand for $/.
but then what about the different index bases for $42 and $/[42]? i
don't think that has been resolved (nor has mixing the $1.1 and $1[1]
syntaxes).
Bear in mind that that reply was posted i
Autrijus Tang <[EMAIL PROTECTED]> wrote:
> class Point {
> has $.x;
> has $.y;
The progress pugs makes is really impressive.
[ ... ]
> Pugs's Parrot codegen backend needs to be updated
Object attribute access, yeah. IMHO Parrot's current implementation is
wrong.
0) class const
Sweet candy! I might actually be able to start executing some of my
code! Will try any day now. -- Darren Duncan
At 8:48 AM +0800 5/11/05, Autrijus Tang wrote:
This works:
rule name { Larry | Matz | Guido }
rule project { Perl | Ruby | Python }
rule description { \s does \s }
88 matches
Mail list logo
