------- Comment #38 from pcarlini at suse dot de 2007-04-27 14:22 ------- (In reply to comment #37) > Thanks for looking at this issue. > > Also consider Andrew's point about useful diagnostics, for example from > comment #4.
Of course, if/when the front-end is changed as I was outlining, diagnostic would be emitted in such cases. > And the followup to that point in #33 which includes field experience on > how other compilers deal with this same option. I.e. from this viewpoint, > getting a compile time error when you use try/catch with -fnoexceptions is a > feature, not a bug. That would be a good argument for my last point: i.e., do not change the semantics of -fno-exceptions, provide instead a new switch, which would be different only in that the front-end would still accept syntactically exception constructs, only would not emit semantics for those. *If* we have that switch, then probably we could *additionally* change the library as you are suggesting, that would provide a complete set of features to the users, in my opinion. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25191
