jolz <[EMAIL PROTECTED]> wrote:
> Driver uses this construct:
> assert(str = (*env)->GetStringCritical(env, v, 0));
> It doesn't work. assert doesn't have to be called in release build.
> It should be:
> str = (*env)->GetStringCritical(env, v, 0);
> assert(str);

The real mistake here is using assert() at all. What I am asserting I
want checked, even in release builds, because returning 0 means
out-of-memory. I should replace all of these with if (str==0) ...
checks, it's just more ugly and most people use the binaries, which I
compile with assertions.

I may change this.

d

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SQLiteJDBC" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups-beta.google.com/group/sqlitejdbc?hl=en
-~----------~----~----~----~------~----~------~--~---

  • bug jolz
    • Re: bug David Crawshaw
    • bug jolz

Reply via email to