On Wed, 17 Sep 2008, Maurilio Longo wrote: Hi Pritpal and Maurilio,
> signals and sync methods are very usefull and common in xbase++ mt programs. > xharbour already has support for both of them (it seems to me that the SYNC > option still has some problems, but it's been a long time since I last checked Harbour has exactly the same functionality using MUTEXES. hb_mutexCreate() -> <pMtx> hb_mutexLock( <pMtx> [, <nTimeOut> ] ) -> <lLocked> hb_mutexUnlock( <pMtx> ) -> <lOK> hb_mutexNotify( <pMtx> [, <xVal>] ) -> NIL hb_mutexNotifyAll( <pMtx> [, <xVal>] ) -> NIL hb_mutexSubscribe( <pMtx>, [ <nTimeOut> ] [, @<xSubscribed> ] ) -> <lSubscribed> hb_mutexSubscribeNow( <pMtx>, [ <nTimeOut> ] [, @<xSubscribed> ] ) -> <lSubscribed> SUBSCRIBE it the same as WAIT and NOTIFY the as SIGNAL. It was not clear for me from the documentation Pritpal sent if xbase++ WAIT internally works like hb_mutexSubscribe() or hb_mutexSubscribeNow(). The valid one should be used. If you need class which will work like in xBase++ then you can implement it in few lines. We do not have yet SYNC methods at all but I'd implemented low level code for then in thread.c and I have to updated yet classes.c. xHarbour have only CLASS SYNC methods but it also does not support normal SYNC methods though it compiles code which uses them but internally convert the function to class methods synchronization. > it), maybe having the same support in harbour could make it easier to move > code from xbase++/xharbour to harbour and vv. Yes. But I'll prefer to create basic function interface which should allow to easy write upper level code like synchronization object in xBase++. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
