== Quote from Jonathan M Davis (jmdavisp...@gmail.com)'s article > On Sunday 18 July 2010 00:46:36 Jonathan M Davis wrote: > > I'll file a bug report > > > > - Jonathan M Davis > Wait. That's not the problem. Or at least, that's not the problem that needs > to > be reported. The problem is that we're not compiling with -w. If you compile > with -w, then statements such as > scope(failure) continue; > won't compile due to being unreachable statements. But if you compile with -w, > then the compiler flags it as an error, and the program fails to compile. So, > I > filed a bug report on the fact that such warnins aren't reported without -w > (though they would still compile since they're warnings rather than errors): > http://d.puremagic.com/issues/show_bug.cgi?id=4482 > Regardless, what you're trying to do is clearly an error, and compiling with > -w > will show that. > - Jonathan M Davis
This should be upped to a error, as -w only shows it as unreachable(without a line number:(. I don't think unreachable code is an error. I often have unreachable code when debugging. case default: assert(false);// temp ... break;
