ailto:[email protected]>]
*Sent:* Wednesday, September 15, 2010 9:02 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [CLucene-dev] Thread handling
If assert really isn't equivalent to the
. If NDEBUG is defined, than
>
> assert it simply ((void)0). May be it behaves differently on other
> platforms.
>
> Jiri
>
>
>
>
>
> *From:* Itamar Syn-Hershko [mailto:[email protected]]
> *Sent:* Wednesday, September 15, 2010 9:02 PM
> *To:* clucene-develope
Jiri
From: Itamar Syn-Hershko [mailto:[email protected]]
Sent: Wednesday, September 15, 2010 9:02 PM
To: [email protected]
Subject: Re: [CLucene-dev] Thread handling
If assert really isn't equivalent to the ASSERT macro, where the statement is
being call
If assert really isn't equivalent to the ASSERT macro, where the
statement is being called but the condition isn't evaluated, this should
probably be changed to reflect this (or moved to such a macro to spare
the extra var).
On 15/9/2010 9:36 AM, Šplíchal Jiří wrote:
Hi,
I found following c
Hi,
I found following code in threads.cpp:
_LUCENE_THREADID_TYPE
mutex_thread::CreateThread(luceneThreadStartRoutine* func, void* arg){
_LUCENE_THREADID_TYPE ret;
assert(pthread_create(&ret, NULL, func, arg) == 0 );
return ret;
}
This code is use
