On Mon, 05 Jan 2009, Francesco Saverio Giudice wrote: Hi Francesco,
> in particular macros: > HB_TEST_CANCEL_ENABLE_ASYN > HB_DISABLE_ASYN_CANC You do not need it. Harbour does not use any OS level thread cancellation code. AFAIK xHarbour code is also not safe for such cancellation so it should be updated (it's not easy job because it needs whole code verifying and adding push/pop cleanup functions for all allocated resources like allocated memory, any OS handles, used work areas, etc) or removed. > as I have understood that > HB_STACK_UNLOCK > HB_STACK_LOCK > should be > hb_vmUnlock(); > hb_vmLock(); In general yes though internally they do not make exactly the same operations. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
