Let me illustrate... - Tasks: task #7061, Set and test stream state...
You are not allowed to post comments on this tracker with your current authentication level.
task #7061: Set and test stream state correctly everywhere
Submitter: | Greg Chicares <chicares> | ||
Submitted: | Thu 05 Jul 2007 06:20:14 PM UTC | ||
Should Start On: | Thu 05 Jul 2007 12:00:00 AM UTC | Should be Finished on: | Thu 05 Jul 2007 12:00:00 AM UTC |
Category: | Quality Conformance | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | chicares | Open/Closed: | Open |
Sat 18 Jul 2009 02:51:13 PM UTC, comment #2: |
Greg Chicares <chicares> |
Sat 18 Jul 2009 11:27:03 AM UTC, comment #1: Unfortunately I have scant recollection of what is this ticket about so I'm not sure what exactly should be done here. I just wonder if there is a reason to not just use basic_ios::exceptions() to switch the streams in exception-throwing mode?
|
Vadim Zeitlin <zeitlin> |
Thu 05 Jul 2007 06:20:14 PM UTC, original submission:
See 20070705T0108Z entry in 'DefectLog'.
|
Greg Chicares <chicares> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-07-18 | chicares | Assigned to | zeitlin | chicares | |
2009-07-18 | zeitlin | Assigned to | etarassov | zeitlin | |
2007-07-05 | zeitlin | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-cf05.
Corresponding source code
basic_ios::exceptions() alone isn't the answer. Consider:
http://cvs.savannah.gnu.org/viewvc/lmi/lmi/calendar_date.cpp?r1=1.17&r2=1.18
All integers are valid as integers, and perhaps they're
all valid JDNs, but they aren't all within the JDN range
for class calendar_date.
Resolving the global issue would require analyzing each
extractor in lmi and guarding against every way it might
fail, in particular following Langer & Kreft's advice to
"care about the output variable of an extractor".
Most aren't worth considering, though, because they occur
in obsolete code that should instead be replaced. Those
in 'ihs_dbvalue.?pp' and 'ihs_pios.?pp' (e.g.) won't be
needed once we convert product databases to xml, and I
have plans to replace 'ihs_server7702io.?pp' as well.
You wouldn't know all these plans, so I've reassigned
this task to myself.