G'day Paul...
Nice to see another Evolution user... :) > It's a more advanced question than most, but not inappropriate for this > list, I think. You may also wish to consider comp.lang.perl.misc or > perlmonks for further insight. Thanks for that... :) > But you should also consider that many of those who could answer your > question were asleep when you posted it. Very true... I think I was responding a bit too soon as normally the response time from this list has been pretty quick. Although, I was wondering if it was getting into more advanced concepts than what may be considered beginners, and wanted to be respectful of that. :) > I'm not certain whether your aim is to ensure that developers > subclassing the superclass do it correctly, or that users don't do > something they shouldn't. Assuming the latter, the perl way of handling Neither... I'm the sole developer on this project... I'm just wanting things done cleanly and logically, so that is obvious enough what is going on. I'm going for cleanly defined class interfaces. Makes the job of ad-hock alterations easier. (Or at least that's what I'm thinking. I'm planning for the future as I know what my boss is like - he won't be likely the slow movement now, but he'll appreciate the ease and speed I do things later.) > The key bit of information you have is the class of your object. You > also have the name of the package you are currently in and the can() > method or function. Ahh.. thanks for that... I think someone else also illustrated this in a creative and what would seem to be a de-facto way. :) Cheers for all that. I appreciate the time you've put into the response. Have a good one! -Mike -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
