in reply to Re^8: quickness is not so obvious
in thread quickness is not so obvious

So you are not allowed to use goatse?

Does this rule also exclude call(i++) ?

Cheers Rolf

PS: Je suis Charlie!

Replies are listed 'Best First'.
Re^10: quickness is not so obvious
by RonW (Parson) on Jan 26, 2015 at 21:21 UTC
    Does this rule also exclude call(i++) ?

    Yes. Increment, decrement and assignment operators are not allowed in expressions that are parameters to functions.

      Increment, decrement and assignment operators are not allowed in expressions that are parameters to functions.

      Sorry, but a quick review of the subthread doesn't reveal why that is so. Could you explain please?


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      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". I'm with torvalds on this
      In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

        It's another guideline I didn't previously mention.

        In theory, it could be considered a corollary to the "assignment and assignment-like ops must be left most op" when you think of function call as a named op. However, I'm pretty sure the people who wrote the guidelines weren't thinking that way. They just were seeking ways to avoid non-obvious side effects.