The detection also appears to only work if the statement has a syntax
error in it.
e.g.
fred:
X=25;echo$$X
With 8 spaces the above is not warned about even though to the human
eye when you use vim's search function to highlight spaces it becomes
visually highly suspicious.
1) it's immediately after a target or
2) immediately after a recipe
3) it's indented which is an odd thing to do outside of any context such as ifeq
I'm not suggesting that there's any truly satisfactory way to be sure
of this but even if an "info" message appeared or an "NB" or if one
had to switch on some special warning mode that was extra picky -
whatever it was would be handy and perhaps discourage people from
using styles that could end up in confusion. 50 years down the line
for gmake 5 our children might then switch from notification to
warning and finally enforcement of something.
Regards,
Tim
On 5 September 2013 11:18, Tim Murphy <tnmur...@gmail.com> wrote:
> ah, interesting - good point. My standard (at least the enforced
> standard where I work) is 4-spaces and it doesn't catch that.
>
> On 5 September 2013 10:44, Eli Zaretskii <e...@gnu.org> wrote:
>>> Date: Thu, 5 Sep 2013 10:38:16 +0100
>>> From: Tim Murphy <tnmur...@gmail.com>
>>> Cc: Byron Hawkins <by...@hawkinssoftware.net>,
>>> Boris Kolpackov <bo...@kolpackov.net>, bug-make <bug-make@gnu.org>
>>>
>>> It would be nice even if make was able to guess what might be
>>> happening and issue a warning
>>
>> It already does:
>>
>> /usr/tmp/Gma07464:2: *** missing separator (did you mean TAB instead of 8
>> spaces?). Stop.
>
>
>
> --
> You could help some brave and decent people to have access to
> uncensored news by making a donation at:
>
> http://www.thezimbabwean.co.uk/friends/
--
You could help some brave and decent people to have access to
uncensored news by making a donation at:
http://www.thezimbabwean.co.uk/friends/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
