I have a co-worker who (imo) over-uses FileHandle and Class::Struct where simply using open or a complex data structure a-la perlreftut would suffice. Both seem to slow his code down, without adding any degree of utility (clarity, maintainability, functionality). At least, in my eyes.
When I get the chance to work on his code, I have to resist the urge to re-write all of the calls to FileHandle and Class::Struct so they "look right". Just because it isn't the way I'd do it doesn't mean it's wrong; it's different.
fwiw, my co-worker likes to use FileHandle because he wants his code to be as object-oriented as possible. I'm not criticising you- I'm genuinely curious: why use FileHandle; in the code you posted?
blyman
setenv EXINIT 'set noai ts=2'
In reply to [OT] Re: How to dynamically (yet structurally) creat a hohohohoh
by belden
in thread How to dynamically (yet structurally) creat a hohohohoh
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |