[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #49093] ifdef checks for non-empty value, not definition

From: Paul D. Smith
Subject: [bug #49093] ifdef checks for non-empty value, not definition
Date: Wed, 14 Sep 2016 22:13:25 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0

Update of bug #49093 (project make):

              Item Group:                     Bug => Documentation          
           Triage Status:                    None => Small Effort           


Follow-up Comment #1:

What the doc is trying to say is that:

ifdef FOO
$(info true)

will not print true because FOO has no value.

However, this:

BAR = $(FOO)
ifdef BAR
$(info true)

_will_ print true.  Even though if you expanded $(BAR) you'd get the empty
string, the variable BAR is not empty (it's set to $(FOO)) and so ifdef calls
it defined.  Probably an example like this would help make the doc more

Yes, it's true that ifdef is badly named.  It should be something like "ifset"
or whatever instead.  However, it works as intended and so does the origin
function value "undefined"; they have had these inconsistent meanings for 20+
years now; they're not going to change.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]