Is there any reasonable replacement to pthread_mutex_timelock()? Saying not to use it doesn't help if you are basically saying the function can't work.
Rick On Fri, Mar 8, 2019 at 6:03 PM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > > > /Users/enrico/ooRexx.svn.rem.src/common/platform/unix/SysSemaphore.cpp:235:12: > error: use of undeclared identifier 'result' > while (result == 0 && !this->postedCount) // Has it been posted? > Spurious wakeups may occur > ^ > /Users/enrico/ooRexx.svn.rem.src/common/platform/unix/SysSemaphore.cpp:237:9: > error: use of undeclared identifier 'result' > result = pthread_cond_timedwait(&(this->semCond), > &(this->semMutex), &ts); > ^ > /Users/enrico/ooRexx.svn.rem.src/common/platform/unix/SysSemaphore.cpp:241:12: > error: use of undeclared identifier 'result' > return result != ETIMEDOUT; > ^ > /Users/enrico/ooRexx.svn.rem.src/common/platform/unix/SysSemaphore.cpp:336:12: > error: use of undeclared identifier 'pthread_mutex_timedlock' > return pthread_mutex_timedlock(&mutexMutex, &ts) == 0; > ^ > 4 errors generated. > > > Easy to fix the result thing > > Please note that > > pthread_mutex_timedlock > > is not part of the POSIX pthreads specifications > > So to provide maximum portability it should not be used, > > E > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
