[mailto:va...@apache.org]
Sent: den 29 november 2017 21:52
To: pylucene-dev@lucene.apache.org
Cc: Jesper Mattsson
Subject: Re: JCCEnv::ExceptionOccurred() returns NULL
On Nov 29, 2017, at 15:42, William Schilp wrote:
I've added our JCC expert Jesper to this.
Regarding shared mode, we're
CEnv::ExceptionOccurred() returns NULL
> On Nov 29, 2017, at 15:42, William Schilp wrote:
>
> I've added our JCC expert Jesper to this.
> Regarding shared mode, we're not quite sure what you mean here, do you
> mean dynamically linked runtime libraries(mscrt##.dll)? We use the /M
> On Nov 29, 2017, at 15:42, William Schilp wrote:
>
> I've added our JCC expert Jesper to this.
> Regarding shared mode, we're not quite sure what you mean here, do you mean
> dynamically linked runtime libraries(mscrt##.dll)? We use the /MD flag to
> visual studio.
I mean: build JCC with shar
I've added our JCC expert Jesper to this.
Regarding shared mode, we're not quite sure what you mean here, do you mean
dynamically linked runtime libraries(mscrt##.dll)? We use the /MD flag to
visual studio.
On Nov 28, 2017 12:42, "Andi Vajda" wrote:
>
> > On Nov 28, 2017, at 11:27, William Schil
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
> 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...
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 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
