comment on

If I was really serious about doing this, I'd be patching base (so that's it's not hardwired to caller(0)) and creating a new module. The new module is because you can't go making base call import() all of a sudden.

The point of my original post was really about the interface and how with some fiddling it can support everything. Whatever preferences people might have for defaults, I'd argue that not supporting all options (when supporting them is essentially zero cost) is definitely not the right thing.

In this case I'm stuck with the current base.pm, so OAOO can't work, something's got to give. If I must break OAOO then I think it's better to break it OAOO :) I don't think I've ever use a base class's name in the body of a module, if I did I was probably doing something very naughty and OAOO would be the least of my worries.

Anyway, it looks like we're only arguing about degrees here rather than principles.

In reply to Re^5: use base 'XYZ' and exporting by fergal
in thread use base 'XYZ' and exporting by japhy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks