head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	99.05.12.00.09.53;	author bkoz;	state dead;
branches;
next	1.1;

1.1
date	99.05.11.23.50.47;	author bkoz;	state Exp;
branches;
next	;


desc
@@


1.2
log
@*** empty log message ***
@
text
@



1) common bugs for 
27.6.2.5.1 output/common requirements 
and
27.6.1.2.1 input/common requirements

replace ios::badbit with ios_base::badbit
replace ios::failbit with ios_base::failbit

In addition, there is no member function called "exception()" in
basic_ios, rather it's called "exceptions()." In particular

"If (exception() & badbit) != 0"
should be
"If (exceptions() & ios_base::badbit) != 0"


2) general questions

 - "If an exception is thrown during input/output then ios_base::badbit is
turned on (this is done without causing an ios::failure to be thrown)
in *this's error state.

How is this to be done? There are no corresponding "nothrow" versions
of setstate. Or, is something like this what was in mind:

try {
  setstate(ios_base::badbit)
}

catch (ios_base::failure& __fail) {
// Do nothing, just eat possible exception objects from above.
}


3) 27.6.2.5.1 output/common requirements clash with 
27.6.2.5.2 Arithmetic Inserters

"If the generation fails, then the formatted output function does
setstate(ios::failbit)"

and then later in paragraph 1 we see

"If failed is true then does setstate(badbit), which may throw an
exception, and returns."

ummm. Which is it, or both?





@


1.1
log
@
1999-05-11  Benjamin Kosnik  <bkoz@@loony.cygnus.com>
	* stl/bits/stl_config.h (__USE_MALLOC): Change underlying allocator.
	Check __USE_MALLOC before defining specializations containing
	__default_alloc_template.
	* src/stl-inst.cc: Here too.
	* bits/basic_string.h: Change.
	* testsuite/make_check_libfree++: More tweaks.
	* testsuite/21/capacity.cc: New file.
	* src/string.cc: Rename to be consistent with other inst files.
	Rename to string-inst.cc.
	* src/string*.cc: Change include.
	* src/wstring.cc: Rename to wstring-inst.cc.
	* src/wstring*.cc: Ditto.
	* src/Makefile.in: Also here.
	* src/Makefile.am: Ditto.
	* src/traits.cc: Remove.
	* src/wtraits.cc: Same.
	Try a new way of organizing documentation, one with synchronicity
	between testsuites and docs subdirectories, and see who yelps.
	* docs/html: Remove, use chapter and subject specific directories
	instead of forcing things immediately into format of
	documentation.
	* docs/text: Same.
	* docs/image: Same.
	* docs/faq/text, docs/faq/html: Remove, put in the docs/faq
	directory and sort by filename and extension.
	* docs/17_intro, 18_support, 19_diagnostics, 20_util, 21_strings,
	22_locale, 23_containers, 24_iterators, 25_algorithms,
	26_numerics, 27_io: Add.
	* docs/17_intro/*: Populate with all the text files. . .
	* docs/index.html: Construct.
	* testsuite/*: Update with same names as the docs subdir.
	* testsuite/results: Where to stash conformance results for the
	different snapshots, so that progress/size/speed issues can be
	tracked over time.
@
text
@@

