[cfe-dev] One more EH patch...

[Fariborz Jahanian]

On May 11, 2009, at 5:11 PM, Daniel Dunbar wrote:
>>
>> 2) Emit an error and let the user know at compile-time that they are
>> generating broken code.
>>
>> My personal preference would be (2), because all of the intervening
>> functions between the @throw and the @catch should be compiled with
>> exception support to work correctly, and it's likely that just  
>> turning on
>> exceptions for the files that throw or catch them will introduce  
>> subtle
>> failures.
>
> #2, definitely.

If we are going to issue error for @try/@catch and when -fexceptions  
is not
specified, then it should be done for runtimes which require special  
libraries to handle
them and at ir-gen time, since ASTs should always be
valid, even with -fno-exceptions. For example, static analyzer should  
continue to work, regardless.

- Fariborz


>
>
> - Daniel
>
>> David
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev