Basically, the reason I've been asking about this is that next::method is
approx 2*sub call plus a hash lookup overhead (note sub call, method calls are
marginally more expensive than sub calls).
Given nobody seems to be using the component in isolation, I was wondering
about collapsing any next::method stuff into a single method, probably in Row.
This would make exactly zero difference if everybody's only subclassing Core,
but would probably give us a noticeable performance improvement.
Thoughts? Comments? Objections?
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
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]/
