[rfc-i] tabs [was: sourcecode indentation]

julian.reschke at gmx.de (Julian Reschke) Tue, 16 February 2016 07:09 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 16 Feb 2016 08:09:53 +0100
Subject: [rfc-i] tabs [was: sourcecode indentation]
In-Reply-To: <F5B55E50-D7AA-427A-932C-37D4872F9BD4@cisco.com>
References: <B7E2CCFD-F56B-4749-B8D2-C3F4CFF3EF5F@cisco.com> <56C2B0E8.7070900@it.aoyama.ac.jp> <F5B55E50-D7AA-427A-932C-37D4872F9BD4@cisco.com>
Message-ID: <56C2CB41.9090807@gmx.de>

On 2016-02-16 07:14, Joe Hildebrand (jhildebr) wrote:
> ...
> I think the current situation is pretty close to 2119's "SHOULD NOT".  You SHOULD NOT put a tab character in <sourcecode>, unless it is absolutely required in the target language.  To deal with this, we could add a tabs="true" attribute to <sourcecode>, and give an error if there's an unintended tab character.
>
> Alternately, we could just say that tab-encrusted Makefile's aren't supported in an RFC, and always throw an error on tabs.  Tabs can be worked around in GNU make (https://www.gnu.org/software/make/manual/html_node/Special-Variables.html):
>
> .RECIPEPREFIX = >
> all:
>> @echo Hello, world
> ...

+1 to disallow TABs, until somebody can show how this becomes a problem 
for something other than a Makefile.

Best regards, Julian