Yuval Kogman wrote:
everyone gets to choose, and another thing I have in mind is the
Transactional role...
DBI::Handle does Transactional;
To the STM rollbacker and type checker thingy this means that any IO
performed by DBI::Handle invoked code is OK - it can be reversed
using the Transa
Stevan Little wrote:
Yes, we have. One thing to consider is that it is much easier to get the
"Role order doesn't matter" thing when they are composed. Once you start
keeping the roles around, you run into the possiblity for such things as
"next METHOD" being executed in Role context. I wont ev
On Sat, 2005-07-23 at 20:41 -0700, Brent 'Dax' Royal-Gordon wrote:
> Piers Cawley <[EMAIL PROTECTED]> wrote:
> > It seems to me, that the way to get at all the instances of a class is to
> > ask
> > the Garbage Collector to do the heavy lifting for us, and ideally I'd like
> > to
> > see this e
Piers Cawley <[EMAIL PROTECTED]> wrote:
> It seems to me, that the way to get at all the instances of a class is to ask
> the Garbage Collector to do the heavy lifting for us, and ideally I'd like to
> see this exposed at the Perl level.
It's entirely possible that Perl will be used on virtual mac
Let's say I have a class, call it Foo which has a bunch of attributes, and I've
created a few of them. Then, at runtime I do:
eval 'class Foo { has $.a_new_attribute is :default<10> }';
Assuming I've got the syntax right for defaulting an attribute, and lets assume
I have, the Perl runtime nee
