Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Well said, though I think "May result in cluttered, difficult to read code" is rather subjective. Commented Jun 11, 2013 at 14:42
  • 2
    How does making the semantics of your code explicit make it difficult to read? Commented Jun 11, 2013 at 14:44
  • 1
    I agree with the others in questioning your "Yes Cons". I think it is almost always the opposite. Commented Jun 11, 2013 at 14:56
  • @Frustrated As subjective as the opposite claim. Meaning, not at all, really. Just hard to measure. Commented Jun 11, 2013 at 21:40
  • 1
    @MasonWheeler: While I agree that explicit parens are very important in many cases, I can see how one can go overboard on making semantics explicit. I find 3 * a^2 + 2 * b^2 easier to read than (3 * (a^2)) + (2 * (b^2)), because the format and precedence is familiar and standard. Likewise, you could (to be extreme) forbid the use of functions and macros (or compilers!) in order to make the semantics of your code more explicit. Obviously I'm not advocating that, but I'm hoping to answer your question as to why there need to be limitations (a balance) on making things explicit. Commented Jun 12, 2013 at 13:45