On Sun, Jul 03, 2005 at 11:53:41AM +0200, demerphq wrote: > Maybe im missing something but that report has a comment that says: > > The trick is making sure it doesn't export when you say "use Test::Builder". > > If Test::Builder itself doesnt have anything in its @EXPORT/@EXPORT_OK > then why should it be an issue?
Well, its really an expression of a worry about accidental behaviors being inherited from or given to Test::Builder. Basically, Test::Builder should not be exporting. But if we go the inheritance route it needs an import routine. Big flashing sign there which says "WRONG RELATIONSHIP!" As mentioned before, the Builder and the Module have a HASA relationship not an ISA. So inheritance from Builder for the Module to get functionality is right out. What I'm likely to do is write a Test::Builder::Module which is a base for the external behaviors of the module, such as exporting. You'll probably not inherit from it but rather it would export its functions, effectively a mixin, but I'm not sure right now. I guess I need to think about what it would do beyond exporting. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.' -- "Witches Abroad" by Terry Prachett
