i'm using JCC in a rather large project where a C++ interface drives a java
application through the JCC interface. the java application makes
considerable use of exceptions (as it should) and the C++ interface needs
to catch the various exceptions and perform various actions based on the
exception
> On Nov 28, 2017, at 11:27, William Schilp wrote:
>
> i'm using JCC in a rather large project where a C++ interface drives a java
> application through the JCC interface. the java application makes
> considerable use of exceptions (as it should) and the C++ interface needs
> to catch the variou
i sort of agree with you. throwing an object through a DLL boundary may be
problematic due to memory allocation/deallocation. but in this case, it's
throwing a pointer (_jthrowable*), which is pretty much the same as
throwing an int...
On Tue, Nov 28, 2017 at 12:42 PM, Andi Vajda wrote:
>
> > O
> On Nov 28, 2017, at 16:09, William Schilp wrote:
>
> i sort of agree with you. throwing an object through a DLL boundary may be
> problematic due to memory allocation/deallocation. but in this case, it's
> throwing a pointer (_jthrowable*), which is pretty much the same as
> throwing an int...
true, but at least in my case, leaking a pointer per exception is not that
big a deal.
i have to contact a team i work with that actually generates the JCC
interface, and they're located in Norway...
On Tue, Nov 28, 2017 at 4:48 PM, Andi Vajda wrote:
>
> > On Nov 28, 2017, at 16:09, William Schi
