4 ms·

Why are people up-voting this? This is a recipe for bugs.

by olliesaunders 17y ago

DrJokepu 17y ago
I think (hope) that it was meant to be funny as opposed to being a serious advice.
- olliesaunders 17y ago
  Oh right. I get it now :-)
- jamesbritt 17y ago
  I've done this with Ruby and set the color to light gray. My co-workers wanted to have C/Java-style parens around damn near everything (except when they didn't; the reasoning to omit them was something along the lines of, "But, see, here it's a DSL." ) They strike me as line noise and make it harder to read many things, so I lightened up the color in my vim syntax files to give the appearance of more white space. I had mixed results. Yes, it was far more readable to me, but there were times when a paren was missing or mistakenly added, or the spacing was off (another coding standard violation), and so on. Now that I code on my own, the new coding standards say no parens unless required by the language. I also changed my syntax coloring back to more clearly show parens.
  - DrJokepu 17y ago
    Heated debates amongst programmers (coworkers) about marginally important questions such as indenting styles, parenthesis usage, naming conventions, source code directory structure, etc. are always very amusing to observe. I usually sit back and just watch the show.
    - jamesbritt 17y ago
      "I usually sit back and just watch the show." Were that always an option. :)
JulianMorrison 17y ago
Light gray, then ;-P Srsly, looking past the brackets is the least problem in reading lisp. The harder part is dealing with the lack of syntax, so you have to remember place structures instead of picking up hints from the punctuation. And in that regard, Pythonic indenting makes it harder.
- eru 17y ago
  Perhaps we should go the Haskell route instead of the Python one?
- coliveira 17y ago
  Some IDEs (Alegro CL, cusp eclipse) display the arguments for all known forms and functions.
  - mahmud 17y ago
    s/some/all/g Nearly every Lisp development environment does that. SLIME, the poster child of excess does this as well. I don't think I matched parenthesis, indented or looked up a documentation since 2005.
  - JulianMorrison 17y ago
    Doesn't help you if what you are trying to do is read code, rather than write it.

Why are people up-voting this? This is a recipe for bugs.

DrJokepu 17y ago

I think (hope) that it was meant to be funny as opposed to being a serious advice.

olliesaunders 17y ago
Oh right. I get it now :-)
jamesbritt 17y ago
I've done this with Ruby and set the color to light gray. My co-workers wanted to have C/Java-style parens around damn near everything (except when they didn't; the reasoning to omit them was something along the lines of, "But, see, here it's a DSL." ) They strike me as line noise and make it harder to read many things, so I lightened up the color in my vim syntax files to give the appearance of more white space. I had mixed results. Yes, it was far more readable to me, but there were times when a paren was missing or mistakenly added, or the spacing was off (another coding standard violation), and so on. Now that I code on my own, the new coding standards say no parens unless required by the language. I also changed my syntax coloring back to more clearly show parens.
- DrJokepu 17y ago
  Heated debates amongst programmers (coworkers) about marginally important questions such as indenting styles, parenthesis usage, naming conventions, source code directory structure, etc. are always very amusing to observe. I usually sit back and just watch the show.
  - jamesbritt 17y ago
    "I usually sit back and just watch the show." Were that always an option. :)

JulianMorrison 17y ago

Light gray, then ;-P Srsly, looking past the brackets is the least problem in reading lisp. The harder part is dealing with the lack of syntax, so you have to remember place structures instead of picking up hints from the punctuation. And in that regard, Pythonic indenting makes it harder.

eru 17y ago
Perhaps we should go the Haskell route instead of the Python one?
coliveira 17y ago
Some IDEs (Alegro CL, cusp eclipse) display the arguments for all known forms and functions.
- mahmud 17y ago
  s/some/all/g Nearly every Lisp development environment does that. SLIME, the poster child of excess does this as well. I don't think I matched parenthesis, indented or looked up a documentation since 2005.
- JulianMorrison 17y ago
  Doesn't help you if what you are trying to do is read code, rather than write it.