Change to search_n
Jonathan Wakely
cow@compsoc.man.ac.uk
Mon Feb 28 15:54:00 GMT 2005
On Mon, Feb 28, 2005 at 06:35:22AM +0000, Dimitris Xochellis wrote:
> Its mainly the expressions like (__last - __first >
> __count) that are producing these warnings. These
> expression will fail to work as expected in case
> __first > __last.
Wouldn't that be an invalid range, which breaks the preconditions of
search_n?
jon
--
Prediction is very difficult, especially about the future.
- Niels Bohr
More information about the Libstdc++
mailing list