This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: sstream
- To: pfeifer at dbai dot tuwien dot ac dot at (Gerald Pfeifer)
- Subject: Re: sstream
- From: Joe Buck <jbuck at possibly dot synopsys dot com>
- Date: Fri, 24 Mar 2000 13:14:42 -0800 (PST)
- Cc: law at cygnus dot com (Jeffrey A Law), bkoz at rcygnus dot com (Benjamin Kosnik), gcc at gcc dot gnu dot org, magfr56 at hotmail dot 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.
libstdc++-almost-3 has improved a lot lately. Unfortunately, I've been
too busy to do libstdc++ tests lately; I encourage people to bang on the
new libstdc++, I hope to have some time after next week. A lot of the
issues blocking it have gone away (including a legal issue: I see it's now
assigned to the FSF, glad to see that was taken care of).
> > 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?
The troubles, if any, will be minor and workaroundable if this isn't done
right (programs that mix stdio and iostreams might need fflush/flush calls
that aren't strictly necessary for the standard).