On Jul 16, 2008, at 9:45 PM, Andrew Bennetts wrote: > I am proposing that it should have exactly one meaning. Callers > will be free to > ignore the return value if they don't need it, and will see zero > difference in > behaviour. Sounds like adding a new method, catchException(...), that returns the exception it catches, would be a reasonable compromise. I can't think of any reason that the method that catches-and-returns needs to be the existing API, which does something different. OTOH, I really don't have a problem with doing a try/except/else myself if that's what I need. -Fred -- Fred Drake <fdrake at acm.org>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4