[boost] [Boost-bugs] [ boost-Bugs-1649001 ] Incorrect usage of bad_write(), bad_seek() etc.

From: SourceForge.net (noreply_at_[hidden])
Date: 2007-01-31 11:09:56

Bugs item #1649001, was opened at 2007-01-31 16:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1649001&group_id=7586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Gareth Sylvester-Bradley (gmsb)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect usage of bad_write(), bad_seek() etc.

Initial Comment:
Incorrect usage of bad_write(), bad_seek() etc. defined in <boost/iostreams/detail/error.hpp>.

In several places in the rest of Boost.Iostreams where these functions are used to construct exceptions, the exceptions aren't then thrown. This is probably unintended.

E.g. restrict.hpp, direct_adapter.hpp and range_adapter.hpp.

P.S. Should there be a tracker category of "iostreams"?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1649001&group_id=7586

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Boost-bugs mailing list
Boost-bugs_at_[hidden]
https://lists.sourceforge.net/lists/listinfo/boost-bugs