[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #47163] description of ifdef directive behavior
From: |
Manoj Srivastava |
Subject: |
[bug #47163] description of ifdef directive behavior |
Date: |
Mon, 15 Feb 2016 22:12:43 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.82 Safari/537.36 |
URL:
<http://savannah.gnu.org/bugs/?47163>
Summary: description of ifdef directive behavior
Project: make
Submitted by: srivasta
Submitted on: Mon 15 Feb 2016 04:12:42 PM CST
Severity: 3 - Normal
Item Group: Documentation
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Component Version: 4.1
Operating System: Any
Fixed Release: None
Triage Status: None
_______________________________________________________
Details:
Hi,
This was reported by a debian user. Please retain a CC to
address@hidden
so that the Debian BTS has a copy of your input.
The manual says:
=============================================================
ifdef variable-name
The ifdef form takes the name of a variable as its argument, not a
reference to a variable. The value of that variable has a non-empty value, the
text-if-true is effective; otherwise, the text-if-false, if any, is effective.
Variables that have never been defined have an empty value. The text
variable-name is expanded, so it could be a variable or function that expands
to the name of a variable.
================================================================
The second sentence of the first paragraph has a grammar error, it looks like
it should read "If the value of that variable..."
Also, "The value has a ... value" seems awkward.
Manoj
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47163>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #47163] description of ifdef directive behavior,
Manoj Srivastava <=