Re^3: perl inheritance

Replies are listed 'Best First'.
Re^4: perl inheritance by Anonymous Monk on Mar 23, 2012 at 20:21 UTC
This smells like a good place for an import method.. What do you think? thanks!	[reply]
Re^5: perl inheritance by tobyink (Canon) on Mar 23, 2012 at 23:06 UTC
No, I wouldn't put it in an `import` module. A `BEGIN` block would be better. If you put it in `import`, you have no guarantee that the `import` method will ever actually be called. It's quite easy to load a module without ever calling the `import` method. Conversely, it's very easy for the `import` method to get called multiple times. I actually do something pretty similar to the technique being discussed in XML::LibXML::Augment. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply] [d/l] [select]
Re^6: perl inheritance by JavaFan (Canon) on Mar 23, 2012 at 23:26 UTC
What's the advantage of using a BEGIN block for that? Do you really think there's something to gain putting those methods in place, before the other methods are compiled?	[reply]
Re^7: perl inheritance by tobyink (Canon) on Mar 24, 2012 at 13:12 UTC
Re^8: perl inheritance by JavaFan (Canon) on Mar 24, 2012 at 13:46 UTC
Re^5: perl inheritance by JavaFan (Canon) on Mar 23, 2012 at 20:27 UTC
Sounds like a bad idea to me. Why do you think that's a good idea?	[reply]
Re^4: perl inheritance by Anonymous Monk on Mar 23, 2012 at 20:35 UTC
this smells like it should go in an import method? What do you think ?	[reply]