From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Joe Buck <jbuck@possibly.synopsys.com>
Cc: Jeffrey A Law <law@cygnus.com>,
Benjamin Kosnik <bkoz@rcygnus.com>,
gcc@gcc.gnu.org, magfr56@hotmail.com
Subject: Re: sstream
Date: Fri, 24 Mar 2000 12:56:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.21.0003242153230.82757-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200002211733.JAA13108@possibly.synopsys.com>
On Mon, 21 Feb 2000, Joe Buck wrote:
> I repeat my request that http://sourceware.cygnus.com/libstdc++/status.html
> be updated, since according to it, v3 is nowhere near ready (but it
> shows the state of the world as of the 2.90.6 snapshot).
That has been done know, as far as I saw, as part of libstdc++-2.90.8.
> Also, what mechanisms will v3 provide to allow syncing between stdio
> and iostreams on platforms such as *BSD that don't use libio in their C
> library?
I didn't find anything about that on the libstdc++ web page and noticed
that none of the BSDs is on the build matrix. Hopefully this doesn't mean
we'll run into troubles on these platforms?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2000-03-24 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 10:20 sstream Benjamin Kosnik
2000-02-16 10:31 ` sstream Joe Buck
2000-02-21 0:22 ` sstream Jeffrey A Law
2000-02-21 0:48 ` sstream Martin v. Loewis
2000-02-21 9:19 ` sstream Joe Buck
2000-02-21 13:54 ` sstream Benjamin Scherrey
2000-02-21 9:33 ` sstream Joe Buck
2000-03-24 12:56 ` Gerald Pfeifer [this message]
2000-03-24 13:15 ` sstream Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2000-03-24 16:08 sstream Benjamin Kosnik
2000-03-25 4:28 ` sstream Gerald Pfeifer
2000-03-25 14:20 ` sstream Marc Espie
2000-03-25 17:34 ` sstream Joe Buck
2000-02-15 15:13 sstream Magnus Fromreide
2000-02-15 23:37 ` sstream Martin v. Loewis
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=Pine.BSF.4.21.0003242153230.82757-100000@deneb.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=bkoz@rcygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@possibly.synopsys.com \
--cc=law@cygnus.com \
--cc=magfr56@hotmail.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).