On 03/26/2011 12:55 PM, Mattias Gaertner wrote:
On Sat, 26 Mar 2011 12:43:58 +0200
patspiper<patspi...@gmail.com> wrote:
[...]
AFAIK when writing your own thread manager you must set it.
Still no excuse for a global variable. Simply registering that thread
manager with some RTL class could automatically return True if the
function IsRTLMultiThreaded(): boolean is called. Global variables are
renowned for being "unsafe" and so 80's style of developing...
improved alternative do exist now.
lol.
Changing a time critical variable to a function just to prevent
vandalism by newbies. For a moment I really thought you were serious. :)
I have to partially agree with Graeme on this point, especially that
this package was ported from Delphi. The symptoms were on the surface
unrelated to the cause. I had to debug for quite a while until I
stumbled upon the culprit IsMultiThread assignment buried deep within
10-15 units. A compile time 'read only' error would have saved me a lot
of grief.
The joke was to use a function.
I was inprecise when I mentioned 'this point'. I was alluding to the
very early posts in this thread, and in particular the read only issue.
My bad.
A read only property would be nice and a separate procedure to set it.
But I don't know if this is compatible.
Too bad. It could save others a lot of frustration.
Stephano
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
