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 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
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 }
