DIP65: Fixing Exception Handling Syntax

[Walter Bright via Digitalmars-d]

On 7/17/2014 2:40 AM, bearophile wrote:
> Walter Bright:
>
>> Breaks existing, working code for little gain. I suggested a fix that deals
>> with the issue and does not break existing code.
>
> This is not yet convincing. Let's talk about the "Pokemon Exception Handling",
> for when you just Gotta Catch 'Em All :-) I think the D/Python code that uses
> this pattern is dangerous/smelly; so you are not breaking valid code, you are
> forbidding a coding pattern that in 99.5% cases good D code should not contain.

At some point we need to stop breaking user code without really strong reasons. 
I don't see that any evidence that people who use such patterns have done so 
erroneously, just a supposition and a made up statistic.

The onus is on a new feature and breaking change to prove its worth, the onus is 
not on those wishing to preserve the status quo.

I.e. it's "why", not "why not" make a breaking change. Especially since it is 
apparently a commonly used coding pattern, appearing 25 times in Phobos alone.