in reply to Re^3: Does eval cause that much of a performance hit?
in thread Does eval cause that much of a performance hit?

I agree with you, except that we've now moved so far from the OPs point: prefer things like a three line if construct than a trailing if., and perrin's response that we're almost on a different subject. 'sides which, the same people that eshew the trailing if also tend to reject the ternary as too complex/confusing/unclear/short.

as an explicit undef is pretty dumb,

I'm not sure where you saw the explicit undef?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^4: Does eval cause that much of a performance hit?

Replies are listed 'Best First'.
Re^5: Does eval cause that much of a performance hit?
by grinder (Bishop) on May 06, 2009 at 15:02 UTC

    I don't think the topic has drifted.

    The point I wanted to make was that a ternary conditional is a viable alternative to introducing a scope (a 3-line if), if statement modifiers are not favoured by local shop practices. (Which is a reasonable edict, even if I don't agree with it myself).

    I'm not sure where you saw the explicit undef?

    There was none. It came about in my snippet from employing a ternary, which requires one to put something "in the else" part.

    • another intruder with the mooring in the heart of the Perl

[reply]

In Section Seekers of Perl Wisdom