Opened 16 years ago

Closed 15 years ago

#822 closed Bugs (fixed)

Incorrect usage of bad_write(), bad_seek() etc.

Reported by: gmsb Owned by: Jonathan Turkanis
Milestone: Component: iostreams
Version: None Severity: Problem
Keywords: Cc:

Description 

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"?

Change History (2)

comment:1 by Daryle Walker, 15 years ago

Component: None → iostreams
Severity: → Problem

comment:2 by Jonathan Turkanis, 15 years ago

Resolution: None → fixed
Status: assigned → closed

The only occurrences I found were in boost/iostreams/detail/adapter/range_adapter.hpp and boost/iostreams/detail/adapter/direct_adapter.hpp (both involving bad_seek()); these are fixed in [42357] in branches/iostreams_dev, to be merged into trunk shortly.

Note: See TracTickets for help on using tickets.