On Monday, February 20, 2023 2:50 PM, Paul Smith wrote:
>On Mon, 2023-02-20 at 14:20 -0500, rsbec...@nexbridge.com wrote:
>> I think you need to be able to return to a compatible mode for some
>> users. Having an option like --undefined-variables=warn or --
>> undefined-variables=error (the default
On Mon, 2023-02-20 at 14:20 -0500, rsbec...@nexbridge.com wrote:
> I think you need to be able to return to a compatible mode for some
> users. Having an option like --undefined-variables=warn or --
> undefined-variables=error (the default) or --undefined-
> variables=ignore would be prudent.
Hm.
On February 20, 2023 2:11 PM, Paul Smith wrote:
>In the next major release (not the upcoming 4.4.1 release but the one after
>that) I
>plan to implement notifying users of invalid variable references; for example
>variable names containing whitespace.
>
>So, a makefile like this for example:
>
>
> On Feb 20, 2023, at 2:11 PM, Paul Smith wrote:
>
> In the next major release (not the upcoming 4.4.1 release but the one
> after that) I plan to implement notifying users of invalid variable
> references; for example variable names containing whitespace.
> ...
>
> The question is, should th
In the next major release (not the upcoming 4.4.1 release but the one
after that) I plan to implement notifying users of invalid variable
references; for example variable names containing whitespace.
So, a makefile like this for example:
all: ; echo $(cat foo)
will notify the user about the il
