News for hackers. Stuff that matters.

A comment on GCC 6: -Wmisleading-indentation vs. “goto fail;”. Parent comment

Re:GCC 6: -Wmisleading-indentation vs. “goto fail;” by ktRolster on Friday February 26, 2016 @11:32AM (#11182269) 

  >I'm glad Python (with semantic whitespace)... solve this problem.
Python solved it....then added the problem of making things you can't even see semantically significant. If you write Python, it's helpful to have an editor that makes the difference between tabs and spaces visible....
[ Parent | on HN ]
Re:GCC 6: -Wmisleading-indentation vs. “goto fail;” by MattConfluence on Friday February 26, 2016 @11:38AM (#11182307)
Since Python 3 the interpreter will halt when detecting mixed whitespace, forcing the programmer to deal with it.

https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces

[ Parent | on HN ]
Re:GCC 6: -Wmisleading-indentation vs. “goto fail;” by Redoubts on Friday February 26, 2016 @04:22PM (#11184343)
> it's helpful to have an editor that makes the difference between tabs and spaces visible....

I do this for any and every language. Mixing tabs and spaces always sucks.

[ Parent | on HN ]
Re:GCC 6: -Wmisleading-indentation vs. “goto fail;” by heinrich5991 on Friday February 26, 2016 @02:02PM (#11183273)
This is only a problem in Python 2.
[ Parent | on HN ]