On Sat, 15 Oct 2011 09:24:36 +0200 "Ludo Brands"
wrote
>On Fri, 14 Oct 2011 20:01:47 -0300 >wrote
>> When the routine being passed as a parameter is in the top >> level of the
>> unit, "PrPublic", all is well; the expected pointers are >> passed. When an
>> identical routine "PrPrivate" is h
On 15.10.2011 01:01, andrew.benn...@ns.sympatico.ca wrote:
As part of an attempt at multi-threading, I have had to move
many things that used to be global into the Implementation
parts of units in order to enforce privacy. When I moved a
routine passed as a parameter and put it inside the routine
> When the routine being passed as a parameter is in the top
> level of the unit, "PrPublic", all is well; the expected pointers are
> passed. When an identical routine "PrPrivate" is hidden inside
> the top level routine "Test_it", the expected 2nd pointer appears
> in place of the first and a
As part of an attempt at multi-threading, I have had to move
many things that used to be global into the Implementation
parts of units in order to enforce privacy. When I moved a
routine passed as a parameter and put it inside the routine
to be threaded, the program ceased to work. I append the
es
