Re: [Harbour] MT - Macro compiled blocks and variables scope

2009-06-16 Thread Pritpal Bedi
Hello Przemek Przemyslaw Czerpak-2 wrote: > > It's default Harbour behavior, just finish your example so it can be > compiled > and executed and make some tests. > I think I have to relook my code and find the exact cause. Will be posting the compilable sample if I found if the issue can be

Re: [Harbour] MT - Macro compiled blocks and variables scope

2009-06-16 Thread Przemyslaw Czerpak
On Tue, 16 Jun 2009, Pritpal Bedi wrote: Hi, > Here is what I am having in my applactions: [...] > // QUESTION: pz1 is initialized in main thread and re-public(d) in another > thread > // because macro is compiled in main thread, pz1 referenced is from > main thread This is not true.

[Harbour] MT - Macro compiled blocks and variables scope

2009-06-16 Thread Pritpal Bedi
Hello Przemek Here is what I am having in my applactions: static aMacros Function Main() Local aStrings, i DefinePublics() aStrings := { 'pz1', 'pz2' } for i := 1 to len( aStrings aadd( aMacros, &( '{|v,w,x,y,z|' + aStrings[ i ] + '}' ) ) next pz1 := 4000 do wh