I'd suggest Hook::LexWrap over Hook::WrapSub.
And not just because I wrote Hook::LexWrap. ;-)
Hook::WrapSub can change the semantics of a wrapped subroutine in
subtle ways (in particular, caller returns different values). | [reply] |
Based on the docs, I'd agree, I'd not heard of Hook::LexWrap: I must have missed it when it came up on the CPAN nodelet. Thanks for filling me in on that. I'll probably play with it soon as it could be very useful to me.
Thanks, --traveler
| [reply] |
| [reply] |
what does this provide over Attribute::Types, Scalar::Properties and the interesting module Hook::WrapSub ?
Psychorigid wasn't thought to be better !
To be honest I even didn't know most of the modules you're talking about...
(I know, shame on me ;-)
However after browsing through their doc, I think I should make clear why psychorigid is different to my mind :
Psychorigid goal is to provide a way to check code without modyfing it.
I mean, there must be no difference between a code using psychorigid and a standard code.
(Ok, I'm cheating on this, as I'm modifying comments...)
What I wanted was a module that I could activate at the debugging phase to get extra checks
and desactivate before sending it to my production server
(by just adding/removing the 'use psychorigid' line...)
Anyway, thanx again for the usefull modules list...
"Only Bad Coders Code Badly In Perl" (OBC2BIP)
| [reply] |