Daryle Walker wrote:
>
> In section 27.1.1 [lib.iostream.limits.imbue], I think the names
> "ios_base" and "basic_ios" have been switched.  The "ios_base" version
> of "imbue" can't induce a call to the "basic_ios" version since the
> inheiritance is the wrong way and the two versions are _not_
> "virutal"-ly related.  It doesn't make sense.  If the names are
> reversed, then it would make sense

Yup, looks like the class names got interchanged. It's an editorial
change, and I've fixed it for the next (March, 2005) working paper.
Thanks.

> especially since sec. 27.4.4.2 para.
> 8-9 already specifies it!

No, they say two different things. These two paragraphs tell you what
basic_ios::imbue does; [lib.iostream.limits.imbue] tell you that nothing
else does those things.

--

Pete Becker
Dinkumware, Ltd. (http://www.dinkumware.com)

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

dwalker07@snet.net (Daryle Walker) writes:

> Sorry if this has already been reported.  I think TC1 has come out, but
> this is for the original 1998 version (so it may have already been
> fixed).
[snip]

See anubis.dkuug.dk for lists of issues, defect reports, and their
    (proposed) resolutions. The defect reports marked as 'TC1' are
    those whose resolutions made it into TC1 .

Also, Andrew Koenig keeps a pdf of the differences between C++1998
    and C++2003 on his website:
    http://www.acceleratedcpp.com/authors/koenig/c++std/revisions.pdf

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]

Sorry if this has already been reported.  I think TC1 has come out, but
this is for the original 1998 version (so it may have already been
fixed).

In section 27.1.1 [lib.iostream.limits.imbue], I think the names
"ios_base" and "basic_ios" have been switched.  The "ios_base" version
of "imbue" can't induce a call to the "basic_ios" version since the
inheiritance is the wrong way and the two versions are _not_
"virutal"-ly related.  It doesn't make sense.  If the names are
reversed, then it would make sense, especially since sec. 27.4.4.2 para.
8-9 already specifies it!

[On a separate note, doesn't 27.1.1 mean that a new stream-buffer class
can't call the "imbue" of a parent(s)?  I mean "parent" either by
inheiritance (usual case) or containment (filter).]

--
Daryle Walker
Mac, Internet, and Video Game Junkie
dwalker07 AT snet DOT net

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]