Re: Opinionated, yet anonymous...?

[Anonymous Monk]

1. If XP doesn't matter, then what matter the originator of the opinion? If the opinion has merit, factor it into your thinking, if not, move and ignore it. Down vote if that makes you feel vindicated.

2. Cargo-cult implies this is rote-learnt behaviour rather than experiential conclusion. Consider from where this behaviour might have been culted.

3 thru 5. You assume too much when you assume the comment was directed at jeffa or any other individual. History is the key. Where did the culted behaviour originate? How and why does it perpetuate?

When the language designers added the /o modifier, they obviously perceived of the circumstance when such optimisation would be useful and beneficial. Dismissal under a catch-all term as a micro-optimisation suggests that the designers were wrong. Its strange how often it is the same voices that routinely attribute the wares of MS, Sun and others as bloated and being part of a conspiracy to fuel the need for hardware and software upgrades, that are the first to condemn those that attempt to write clean, efficient, optimal perl code.

Add this to the list of other perl features equally dismissed in this place as being non-useful: symbolic references, global variables, goto, c-style for loops, regexen of any complexity, while loops whith implicit assignment to $_ and all the other things that have variously been "condidered harmful".

[jeffa]

"Dismissal under a catch-all term as a micro-optimisation suggests that the designers were wrong."

I disagree. I interpret that to mean "use with caution". eduardo knows me. He asked me a damn good question and i answered with my opinion. No where did anybody say that the designers of Perl should be "embroiled, confused and kept in the quagmire" for adding the o modifier.

"Add this to the list of other perl features equally dismissed in this place as being non-useful ..."

Who said obfuscation is non-useful? :P

Oh, and even if you didn't directly direct the comment at me, you did so indirectly by replying directly to me. :) (one self-ascribed expert ... oooookay)

Sigh ... all of this bitterness ... i think it's PEANUT BUTTER JELLY TIME!!!

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

[broquaint]

Add this to the list of other perl features equally dismissed in this place as being non-useful

This is an unforunate truth, but another unforunate truth is that while all those features serve a purpose, and it serve it well, they can be easily mis-used and are therefore discouraged (said discouragement usually occurs when the constructs are mis-used). It's the same with almost any feature in perl (and any language for that matter), it's no good to sprinkle it about the code because it's there you have to have an understanding of what the construct does and where it is appropriate to use it.
HTH

_________
broquaint