🚀 go-pugleaf

Brian Glendenning wrote:
> 
> In a different topic, I'm confused about the different purpose ascribed to
> exceptions derived from logic_error:
> [snip]
> 
> and runtime_error:
> [snip]
> 
> It seems to me that with this wording most exceptions should be derived from
> runtime_error.
> However, basic_string<...>::remove(size_type pos = 0, size_type n = npos),
> for example, throws out_of_range (derived from logic error).
> 
> Unless the program only runs with manifest constants, it can't detect this
> problem before the program executs:
>         cin >> pos; mystring.remove(pos);
> 
> So why does it throw a logic_error rather than a runtime_error? Thanks!
> 
> (I'm also interested in learning whether it's a good idea to derive our
> exceptions from standard exceptions).
> 

Your code should have encountered that condition during 
development, or you should have seen it coming, so you should 
have logic built in to supply correct values to remove in all 
cases.

-- 
Robert Stewart		| My opinions are usually my own.
Datalytics, Inc.	| stew@datalytics.com
---
[ comp.std.c++ is moderated.  To submit articles: try just posting with      ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu         ]
[ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
[ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
[ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]