Brandon Black wrote: > On 11/22/06, Christopher H. Laco <[EMAIL PROTECTED]> wrote: >> Basically, I was calculating the super_path all of the time, rather than >> checking the current class variable first...and with a little extra >> caching of the super_path returned from Class::ISA, things take about >> 1/4 the time they used to for get_inherited based accessors. >> > > Has any thought been given to the fact that our method resolution > order is C3, but CAG resolution will be standard depth-first @ISA via > Class::ISA? Perhaps we should make a subclass C::A::G::C3 that > interacts with Class::C3 (an alternative would be for C::A::G to > detect the usage of Class::C3 and automatically act accordingly). > >
I did. That's why I put the bits into ->get_super_paths :-) I figured a C3 issue was only a matter of time. I was torn whether that method, or get_inherited should deal with the caching... and stuck with get_inherited. I'd say it's worth putting a subclass in the same dist. Hell, I'd even do it if someone can point me in the right C3 direction... -=Chris
signature.asc
Description: OpenPGP digital signature
_______________________________________________ List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class Wiki: http://dbix-class.shadowcatsystems.co.uk/ IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/ Searchable Archive: http://www.mail-archive.com/[email protected]/
