From: "Noel L Yap" <yap_noel@jpmorgan.com>
To: christoph.loewe@gameplay.de
Cc: Cygwin@Sourceware.Cygnus.Com
Subject: Re: G++ and ISO C++ conformity?
Date: Wed, 06 Sep 2000 05:56:00 -0000 [thread overview]
Message-ID: <85256952.0046F281.00@nyc-ntgw-n01.ny.jpmorgan.com> (raw)
christoph.loewe@gameplay.de on 2000.09.06 06:01:04
>I have recently downloaded the latest Cygwin archive
>to start a project in C++. I have read Bjarne Stroustrup's
>"The C++ Programming Language" (Special Ed.) and was surprised
>to find several includes and functions missing in the g++
>distribution.
>
>Header files that could not be found:
> <limits> e.g. numeric_limits<int>::max();
> <sstream> e.g. ostringstream ost;
>
>Furthermore the "range controlled" indexing via at()
>would not work.
>
>Can it be that G++ does not completely support ISO C++?
>Or did I forget to install something?
>Is an update planned, if indeed some features of ISO C++
>are indeed missing in g++?
Books aren't the best sources to get the latest standard. I haven't been
following g++ or C++ in a while so I can't comment on how conformant g++ is, but
I would look through the web to find the latest standard. The latest one I have
is dated 2 December 1996.
Noel
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-06 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 5:56 Noel L Yap [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-07 1:50 Schaible, Joerg
2000-09-06 6:12 jens
2000-09-06 2:58 christoph.loewe
2000-09-06 9:18 ` Ryan B. Caveney
2000-09-09 12:29 ` Jason Craig
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=85256952.0046F281.00@nyc-ntgw-n01.ny.jpmorgan.com \
--to=yap_noel@jpmorgan.com \
--cc=Cygwin@Sourceware.Cygnus.Com \
--cc=christoph.loewe@gameplay.de \
/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).