On Thu, Aug 10, 2006 at 10:28:47 -0700, Rodney Broom wrote: > Disliking the fact that require() doesn't call my import(), I'm > trying to figure out why Catalyst (and so many other things) use > require() over use(). I have to think there's a good reason that > just isn't occuring to me.
Joel already explained the runtime vs. compile time thing... The other issue is that importing is usually not something you want to do unless you're a direct user of a module, and you usually only want to do it if it's an imperative interface (As opposed to OO, etc). Since Catalyst usually uses OO modules, which don't do imports anyway, and it usually loads them on behalf of other code, calling import is not appropriate. -- Yuval Kogman <[EMAIL PROTECTED]> http://nothingmuch.woobling.org 0xEBD27418
pgpVg78DrFZwh.pgp
Description: PGP signature
_______________________________________________ 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/
