While .NET has exceptions, C does not. And so, since C is the basis for all other language bindings we have to get creative to support catching exceptions in C.
Because pretty much everything in .NET can throw and there are no guarantees about what can and what can't throw this is actually a pretty big deal.
The way we solved it is to have an "out" parameter (double pointer in C) appended to almost every .NET API that we generate bindings for. Then, in the implementation, we wrap the actual method call in a try/catch block and set the exception parameter to the caught exception or null if the method did not throw.
Currently, the only exceptions (pun intended) are field getters and setters. As far as I'm aware, these can never throw.
So here's an example of how that looks in practice:
When calling the WriteLine method from C, you should provide a reference to a System_Exception_t object which, after the method call will either be null or contain a value which indicates the method did throw.
While .NET has exceptions, C does not. And so, since C is the basis for all other language bindings we have to get creative to support catching exceptions in C.
Because pretty much everything in .NET can throw and there are no guarantees about what can and what can't throw this is actually a pretty big deal.
The way we solved it is to have an "out" parameter (double pointer in C) appended to almost every .NET API that we generate bindings for. Then, in the implementation, we wrap the actual method call in a try/catch block and set the exception parameter to the caught exception or null if the method did not throw.
Currently, the only exceptions (pun intended) are field getters and setters. As far as I'm aware, these can never throw.
So here's an example of how that looks in practice:
C#:
C:
When calling the
WriteLinemethod from C, you should provide a reference to aSystem_Exception_tobject which, after the method call will either be null or contain a value which indicates the method did throw.