Catch statements that are not in best-match order are a compile time error, g++ does that as a warning too.On Tue, Feb 21, 2012 at 03:15:19PM -0600, Andrei Alexandrescu wrote: [...]A more debatable aspect of exceptions is the first-match rule in catch blocks. All of OOP goes with best match, except here. But then all code is together so the effect is small.Does it make sense to make it best-match? Or is that too risky since everyone expects it to be first-match?
On Tue, 21 Feb 2012 23:29:32 +0100, H. S. Teoh <[email protected]>
wrote:
- Re: The Right Approach to Exceptions H. S. Teoh
- Re: The Right Approach to Exceptions Juan Manuel Cabo
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions Jonathan M Davis
- Re: The Right Approach to Exceptions deadalnix
- Re: The Right Approach to Exceptions H. S. Teoh
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions H. S. Teoh
- Re: The Right Approach to Exceptions deadalnix
- Re: The Right Approach to Exceptions Martin Nowak
- Re: The Right Approach to Exceptions Jose Armando Garcia
- Re: The Right Approach to Exceptions Jacob Carlborg
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions Juan Manuel Cabo
- Re: The Right Approach to Exceptions Juan Manuel Cabo
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions H. S. Teoh
- Re: The Right Approach to Exceptions Andrei Alexandrescu
- Re: The Right Approach to Exceptions Juan Manuel Cabo
- Re: The Right Approach to Exceptions Juan Manuel Cabo
