At 2:21 PM -0500 2/25/04, Simon Glover wrote:
(You're probably getting sick of these by now...)
Should asking for a non-existant attribute cause Parrot to throw an
exception. Currently, it doesn't seem to be able to make up its mind
[snip]
but if we ask for an attribute with an offset >= 2
or
(You're probably getting sick of these by now...)
Should asking for a non-existant attribute cause Parrot to throw an
exception. Currently, it doesn't seem to be able to make up its mind
-- this:
newclass P1, "Foo"
find_type I0, "Foo"
new P2, I0
getattribute P3, P2, -2
ge
At 1:51 PM -0500 2/25/04, Simon Glover wrote:
Currently, calling get_integer on a ParrotClass returns the attribute
count, so you can do:
newclass P1, "Foo"
addattribute P1, "foo_i"
addattribute P1, "foo_j"
set I1, P1
print I1
and the code will print '2'. Will this be part of
Currently, calling get_integer on a ParrotClass returns the attribute
count, so you can do:
newclass P1, "Foo"
addattribute P1, "foo_i"
addattribute P1, "foo_j"
set I1, P1
print I1
and the code will print '2'. Will this be part of the new API, or is it
simply a relic of t