Re: [Harbour] dbeval incompatibility

2008-03-12 Thread Przemyslaw Czerpak
On Wed, 12 Mar 2008, Przemyslaw Czerpak wrote: > I'll check if I can easy extract only this fix and commit. I've checked and I can extract it and also some other minor fixes and cleanups but without new code. I'll commit them together to avoid problems with future synchronization. best regards, P

Re: [Harbour] dbeval incompatibility

2008-03-12 Thread Przemyslaw Czerpak
On Wed, 12 Mar 2008, Saulius Zrelskis wrote: > > In general for _ALL_ evaluated user codeblocks RDD should set and > > restore current workarea. > and as you know very well, Clipper for this purpose uses waEvalBlock method, > which does this work Yes, it is. We should also add protection against o

Re: [Harbour] dbeval incompatibility

2008-03-12 Thread Saulius Zrelskis
2008/3/12, Przemyslaw Czerpak <[EMAIL PROTECTED]>: > In general for _ALL_ evaluated user codeblocks RDD should set and > restore current workarea. and as you know very well, Clipper for this purpose uses waEvalBlock method, which does this work Best regards, Saulius

Re: [Harbour] dbeval incompatibility

2008-03-12 Thread Przemyslaw Czerpak
On Wed, 12 Mar 2008, Saulius Zrelskis wrote: > Hi, all > There is letter in xHarbour forum from Anatole Kolotovkin > ("dbeval incompatibility", 2008.02.25 10:07) > and it is relevant for Harbour too. > IMHO it must be included in dissonance with Clipper list. I know about it and this message does