Hi, Is this solved if I rename it to __MUTEXWAITERCOUNT()?
I'm fully neutral what to do with this function (well that's not entirely true since it would be better to have something without internal racing conditions and apps not using internal functions). So we can also remove it (but it means readding internals to uhttpd2 code), or maybe there is better solution which uses only safe HB_MUTEX*() calls to solve Mindaugas's problem? What to do? Brgds, Viktor On Mon, Jun 15, 2009 at 9:36 PM, Przemyslaw Czerpak<dru...@acn.waw.pl> wrote: > On Mon, 15 Jun 2009, vszak...@users.sourceforge.net wrote: > > Hi, > >> 2009-06-15 20:44 UTC+0200 Viktor Szakats (harbour.01 syenar.hu) >> * include/hbextern.ch >> * source/vm/thread.c >> + Added HB_MUTEXWAITERSCOUNT() to core. >> (slightly rewritten using local functions) > > Such function by definition cannot return valid result so it should > be marked as helper function with intentional race condition inside. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
