* Dave Rolsky <[EMAIL PROTECTED]> [2007-04-26 21:25]: > I'd say that declaring it where it is used _is_ the best way to > do it. > > It doesn't hurt to declare what prereqs a module has at the top > of a module, and it'll make it clearer what it's using. This is > doubly true when you're importing functions into a new > namespace. It's really annoying to see some random function > used in a module and then try to figure out where it might've > come from.
Agreed, totally agreed, completely and utterly and entirely agreed. ++ and all that, 200 times over. Don’t make stuff happen magically due to remote interactions. That is a nightmare to maintain. Make your immediate dependencies explicit. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
