Tabs, spaces and your salary – how is it really?

Re:Tabs, spaces and your salary – how is it really? by leggomylibro on Tuesday June 20, 2017 @12:21PM (#14595904)

That quote reminds me of one of Joseph Campbell's - "computers are like Old Testament gods; lots of rules and no mercy."

And to go along with that, some things like GNU Make still requires tabs, which is definitely annoying when you have your editor set to autoconvert. And some sects like Go or Python don't technically REQUIRE one or the other, but still try to aggressively purge the heretics.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by Sean1708 on Wednesday June 21, 2017 @07:07AM (#14602658)

> which is definitely annoying when you have your editor set to autoconvert

Is this actually a problem? Every editor I've ever used has detected that I'm writing a makefile and has changed the indentation to tabs automatically.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by linkregister on Tuesday June 20, 2017 @12:59PM (#14596277)

    go fmt

Controversy solved for one language ;)

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by rjeli on Tuesday June 20, 2017 @02:51PM (#14597376)

And clang-format[0] for C/C++, google-java-format[1] for Java, YAPF[2] for Python, rustfmt[3] for Rust...

[0]: https://clang.llvm.org/docs/ClangFormat.html

[1]: https://github.com/google/google-java-format

[2]: https://github.com/google/yapf

[3]: https://github.com/rust-lang-nursery/rustfmt

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by mjevans on Tuesday June 20, 2017 @06:18PM (#14599078)

The parent post's point wasn't about add-on formats. The point was that the language spec it's /self/ has an included lint tool to eliminate controversy.

The go language has /a/ (single) correct formatting syntax.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by na85 on Tuesday June 20, 2017 @12:33PM (#14596026)

Is that a limitation in GNU Make or is it an inherited limitation of m4?

In my experience, m4 is an arcane bit of software that surprisingly few people know about and one that frankly should have been replaced years ago.

Personally, I try to never use autoconf because of this.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by dasyatidprime on Tuesday June 20, 2017 @12:48PM (#14596172)

Tab as the prefix for command lines is a property of all Makefile formats I'm aware of (though not of many other build script formats). Make itself (including GNU Make) does not generally use M4, though both Autoconf and Automake use it, often in conjunction with Make, as part of the Autotools suite which is also published by GNU.

So, none of the above, in itself. It is a historical anomaly which has been preserved.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by khedoros1 on Tuesday June 20, 2017 @01:13PM (#14596420)

I haven't dug into it, but Wikipedia claims that Make is actually about a year older than M4 (obviously not GNU Make).

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by eternauta3k on Tuesday June 20, 2017 @01:00PM (#14596292)

TIL vim has been hiding this problem from me.

[ Parent | on HN ]

Re:Tabs, spaces and your salary – how is it really? by knome on Tuesday June 20, 2017 @02:42PM (#14597315)

emacs' makefile-gmake-mode, loaded automatically for makefiles, also hides this. I've set indent-tabs-mode to nil in my .emacs for years, but the mode knows it's needed, and will indent the line with a highlighted tab ( until you begin writing in the command to follow it, when it unhighlights it ).

[ Parent | on HN ]