Re: Re: Re: OO-style modifiers for 'sub' ?

[trs80]

I don't think your idea is evil in anyway. I like Perl because it is flexible and it lets you do what you want and assumes you know what you are doing.

I can see where doing the type of checking you are talking about could limit your debugging time. That time savings would be increased as the number of developers having to interact with new code increases. Not knowing the coding environment it is difficult for anyone say if all the checks are really needed in the long run. It might be nice to be able to put the checks into their own method or function that could be overridden via configration variables, that is bypass the tests entirely under certain conditions.

Another module that you might want to check out is Params::Validate.

[Gilimanjaro]

Bunch of good points!

The environment I'm building the code for is one where about five or six people will end up using my code, and maybe expanding it... I figured doing these kind of checks and giving some solid feedback about errors would make the modules & methods easier to handle.

I think I know pretty much what I'm doing, so I like the flexibility. I can't vouch for the experience the people that will use the code have, so that's why I'd like to do some checking...

I like your idea of being able to bypass the checks a lot; the development environment would always use the checks, but the production environment wouldn't, speeding up the application. In that context, it may be an idea to build a module to set up wrappers (maybe using the sub wrapping module Aristotle suggested), which do the checking. It could then be enabled by a single use statement with a list of method names as a parameter...

I can't wait to start tinkering! But sleep comes first... :)