in reply to Re^3: Perl vs C
in thread Perl vs C

I think we both might be right on this question. There is one issue of lvalue calculation in a single statement. Then there is the issue of what happens in a sub call with say foo (++I, --I). In C, we don't know whether "I" will get incremented or decremented first. This is like when you go to the doctor and you say, "it hurts when I press here", and he says, "don't do that".

The fact that we are "arguing" about some syntax says to me that the syntax isn't clear enough. I am not gonna argue precedence.. Hey, that there is even a question at this level means it the code was not clear enough to begin with!

Think about what will happen say 2 years from now? My opinion is that clear code is good code.

Replies are listed 'Best First'.
Re^5: Perl vs C
by ikegami (Patriarch) on Mar 14, 2009 at 23:04 UTC

    In C, we don't know whether "I" will get incremented or decremented first.

    Yes, you've already said that. And you said it was the same for Perl. I replied that in Perl, you do know.

    The fact that we are "arguing" about some syntax

    Since when were we talking about syntax? Our posts are entirely about operand evaluation order.

    I am not gonna argue precedence.

    Since when were we talking about operator precedence? Our posts are entirely about operand evaluation order.

    Think about what will happen say 2 years from now?

    Nothing. Operand evaluation order has been unchanged for at least a decade, probably since day one, and its the intention of developers not to change it. They couldn't even if they wanted because it would break existing in subtle ways.

    My opinion is that clear code is good code.

    Of course. And I gave two examples of clear code that relies on operand evaluation order.

[reply]

In Section Seekers of Perl Wisdom