On Mon, 2024-03-25 at 18:47 -0700, Kaz Kylheku wrote: > > I have considered doing this, but only AFTER it becomes an error > > (not just a warning) to create a make variable with whitespace in > > the name. > > Could you elaborate? How recent of a gmake do we need for this > diagnostic?
The current Git version (next release) will warn about variables created with spaces in the name, regardless of how they get there: $ cat Makefile define a b c $(info hello) endef $ ./make Makefile:1: warning: invalid variable name 'a b c' make: *** No targets. Stop. This can be turned into an error via: $ ./make --warn=error -f /tmp/x1.mk Makefile:1: *** invalid variable name 'a b c'. Stop. There's nothing wrong with creating a variable name containing a comma and I don't anticipate making this illegal.
