Implement unary is-defined operator ?, prohibit undefined .IF argument, remove .IFDEF
boeckmann opened this issue · comments
At the moment ?
is used to return an undefined value. But the following usage seems to be more convinient:
.IF ?VICE
.ENDIF
Testing for undefined value should be much more common than expressing an undefined value. Undefined value will become .?
.
Undefined arguments to .IF can be prohibited. .IFDEF is redundant and can be removed. Both not decided yet.
? and .? are implemented by dd2eda9. Regarding .IF and .IFDEF, a final decision is not made yet.
Problem is, most developers are used to working with if/ifn/ifdef/ifndef, and only a few use the more esoteric ? operators, even more so if those developers are also using C or C++ ..
I am not going to do this, unless I get specific requests for it.
On Wednesday, April 26, 2023 at 03:56:39 AM EDT, Bernd Böckmann ***@***.***> wrote:
At the moment ? is used to return an undefined value. But the following usage seems to be more convinient:
.IF ?VICE
.ENDIF
.IFDEF is then redundant and could get removed. The undefined value becomes .?.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
leave .ifdef, .ifndef in for now.