Why wouldn't you, as you write, use the the fastest access methods
available? Surely you'd want to develop habits that will a) provide
better performance and b) as mentioned below avoid the thorny
side-effects of req->params(). This isn't a matter of premature
optimisation but simply establishing good practise.
Because if you are working with, say, 10 people on a team, and you will
have everyone merrily doing direct hash accesses, sooner or later,
someone's going to fuck it up and something will break in a spectacular
fashion.
If you have methods to do this, the methods can check various things,
and throw out the proper errors.
Yes, a little bit of overhead -- the cost of hardware to compensate for
this overhead is still less than the cost of a fuckup that will keep
your app bugging for the rest of it's lifetime.
--
Ben van Staveren
phone: +62 81 70777529
email: [email protected]
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
