public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Schaible, Joerg" <Joerg.Schaible@gft.de>
To: "Ryan B. Caveney" <Ryan.B.Caveney@saic.com>,
	cygwin@sourceware.cygnus.com
Subject: RE: G++ and ISO C++ conformity?
Date: Thu, 07 Sep 2000 01:50:00 -0000	[thread overview]
Message-ID: <C2D7D58DBFE9D111B0480060086E9635021D9E0C@mail.gft.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Hi Ryan,

> > Header files that could not be found:
> >      <limits>   e.g. numeric_limits<int>::max();
> >         <sstream>  e.g. ostringstream ost;
>
> what I can say is that the stringstream stuff is there -- 
> it's just named
> differently.  On my Cygwin (1.1.2 base), /usr/include/g++-3/ contains
> strstream, not sstream, and the classes it defines are called 
> things like
> ostrstream, not ostringstream.  HTH.

Sorry to say, but you're wrong. The headers and classes you detected were
part of the ANSI-C++ 2.0 spec, the others are part of ANSI-C++ 3.0 and
should be there.

limits: it is known that it is missing
sstream: new IO classes are in development and hopefully ready soon

Try www.STLport.org

Jörg

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-09-07  1:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-07  1:50 Schaible, Joerg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-06  6:12 jens
2000-09-06  5:56 Noel L Yap
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=C2D7D58DBFE9D111B0480060086E9635021D9E0C@mail.gft.de \
    --to=joerg.schaible@gft.de \
    --cc=Ryan.B.Caveney@saic.com \
    --cc=cygwin@sourceware.cygnus.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).