From: "Daniel." <danielhilst@gmail.com>
To: "Curry, Matthew Leon" <mlcurry@sandia.gov>
Cc: "linux-c-programming@vger.kernel.org"
<linux-c-programming@vger.kernel.org>
Subject: Re: [EXTERNAL] Is defined() macro portable or GNU only?
Date: Thu, 1 Oct 2015 10:11:30 -0300 [thread overview]
Message-ID: <CAF3SDA4B=sKK_smuRspwQY6D19XWAgCRn89qWt-vW71y51TBdQ@mail.gmail.com> (raw)
In-Reply-To: <D231AF64.FCEF%mlcurry@sandia.gov>
Thank you Matthew!
Regards,
- dhs
2015-09-30 18:27 GMT-03:00 Curry, Matthew Leon <mlcurry@sandia.gov>:
> It¹s part of ANSI C, and is described in K&R.
>
> Matthew
>
> On 9/30/15, 1:25 PM, "linux-c-programming-owner@vger.kernel.org on behalf
> of Daniel." <linux-c-programming-owner@vger.kernel.org on behalf of
> danielhilst@gmail.com> wrote:
>
>>Hi all,
>>
>>I used to check definitions with #ifdef, but in cases where
>>multiple macros are checked I use #if defined(foo) && defined(bar).
>>Is this defined() check portable/standard? Or is some kind of
>>extension added by GCC?
>>
>>Regards,
>>- dhs
>>--
>>"Do or do not. There is no try"
>> Yoda Master
>>--
>>To unsubscribe from this list: send the line "unsubscribe
>>linux-c-programming" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
"Do or do not. There is no try"
Yoda Master
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-10-01 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 19:25 Is defined() macro portable or GNU only? Daniel.
2015-09-30 21:27 ` [EXTERNAL] " Curry, Matthew Leon
2015-10-01 13:11 ` Daniel. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF3SDA4B=sKK_smuRspwQY6D19XWAgCRn89qWt-vW71y51TBdQ@mail.gmail.com' \
--to=danielhilst@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mlcurry@sandia.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).