From: Eljay Love-Jensen <eljay@adobe.com>
To: Michael Svetlik <m.svetlik@ssi-schaefer-peem.com>, gcc-help@gcc.gnu.org
Subject: Re: Where should g++ find a 'max' macro or function ?
Date: Tue, 11 Nov 2003 13:19:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20031111071637.01577218@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <200311101930.22097.m.svetlik@ssi-schaefer-peem.com>
Hi Michael,
I usually look in the C++ header files themselves. Note: some compilers (*cough* Microsoft *cough) are not ISO 14882 compliant/up-to-date, and may put the symbols in the incorrect header file (if not missing the sanctioned symbol entirely)... so some caution is warranted.
Or I refer to "The C++ Programming Language" (3rd ed, or special ed) by Bjarne Stroustrup.
If you are a glutton for punishment, the ISO 14882 specification is the gospel. But it's not light reading. Cures insomnia, though.
HTH,
--Eljay
prev parent reply other threads:[~2003-11-11 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 12:17 Michael Svetlik
2003-11-10 12:53 ` Eljay Love-Jensen
2003-11-10 18:31 ` Michael Svetlik
2003-11-11 13:19 ` Eljay Love-Jensen [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=5.2.1.1.0.20031111071637.01577218@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=m.svetlik@ssi-schaefer-peem.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).