Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread RoddGraham
Przemyslaw Czerpak-2 wrote: > > Nice to see your messages again. > I am always lurking out here. Nice to see you are still aggressively involved in Harbour. I assume you are still disconnected from xHarbour based upon our communications a year ago (or so). Przemyslaw Czerpak-2 wrote: > >

Re: [SPAM] Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread Przemyslaw Czerpak
On Fri, 26 Sep 2008, Alex Strickland wrote: Hi Alex, > From Pritpals message about xbase++ behaviour dated 2008/09/17 01:12 AM: > Exchanging alias names between work spaces always involves a virtual work > space, the Zero space. Function DbRelease() releases the alias name of a > work area in the

Re: [SPAM] Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread Alex Strickland
Przemyslaw Czerpak wrote: I'll create code to test the relations and lock behavior in released workarea. From Pritpals message about xbase++ behaviour dated 2008/09/17 01:12 AM: Exchanging alias names between work spaces always involves a virtual work space, the Zero space. Function DbRelease

Re: [SPAM] Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread Przemyslaw Czerpak
On Thu, 25 Sep 2008, Angel Pais wrote: Hi Angel, > First of all I must say you are right, this code isn't thread safe: > lInUse := ! lInUse > But i've also said its only a simplification. > In a real program this code: > 1- goes inside a sync method of a class > 2- the logical var does not exit >

Re: [SPAM] Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread Przemyslaw Czerpak
On Thu, 25 Sep 2008, Pritpal Bedi wrote: Hi Pritpal, > > why should I as a Xbase++ developer help a competitor to advance its > > product??? > > And why do you ask for our help in the Xbase++ generic newsgroup? In my > Please do not understand me wrong. Sorry, I was wrong. I hope that you aske

Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-26 Thread RoddGraham
Przemyslaw Czerpak-2 wrote: > > In this code we have: >lInUse := ! lInUse > To make this code MT safe the above line has to be one atomic > operation in xBase++. Is it true? > This is not true in Xbase++. Each variable access (read and write) is serialized independently which guarantees v

Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-25 Thread Angel Pais
Hi Przemek First of all I must say you are right, this code isn't thread safe: lInUse := ! lInUse But i've also said its only a simplification. In a real program this code: 1- goes inside a sync method of a class 2- the logical var does not exit 3- the array is a var of the class 4- the class is

Re: [Harbour] [SPAM] Re: Request to share MT knowledge on Xbase++ NG

2008-09-25 Thread Pritpal Bedi
Przemek > why should I as a Xbase++ developer help a competitor to advance its > product??? > And why do you ask for our help in the Xbase++ generic newsgroup? In my Please do not understand me wrong. I know you have implemented far superior MT design than Xbase++, I swear. My point was to gat