@nogc required on C API callbacks?

Brian Schott via Digitalmars-d digitalmars-d at puremagic.com
Wed Jul 9 13:08:18 PDT 2014


On Wednesday, 9 July 2014 at 19:59:21 UTC, Walter Bright wrote:
> I agree that callbacks shouldn't throw. The problem is existing 
> code uses callbacks that aren't annotated with 'nothrow', and 
> we don't like breaking all their code.

I was talking about @nogc (added in April, so before the 2.066 
beta and after the 2.065 release). nothrow has been there since 
2012 according to git blame, so nothrow is not what's causing the 
signal handling code to not compile.


More information about the Digitalmars-d mailing list