Hi Giuliano,
I was not talking hypothetical example.
All of our products use this technology. Again, what you are telling me is
some suggestion for probable solution, but even when you do it, you
immediately add additional code and containers (list) just to support it due
to the lack of ref counting.
This immediately allows me to argue that your solution will use more memory
and will be slower as it needs additional containers and support code
altogether. So you basically are reconfirming yet again the advantages of
using ref. counting.
With best regards,
Boian Mitov
-------------------------------------------------------
Mitov Software
www.mitov.com
-------------------------------------------------------
-----Original Message-----
From: Giuliano Colla
Sent: Tuesday, September 23, 2014 2:11 AM
To: FPC developers' list
Subject: Re: [fpc-devel] Suggestion: reference counted objects
Il 22/09/2014 23:04, Boian Mitov ha scritto:
However you attempt to apply reference counting in this scheme, you'll
realize that either it doesn't work at all, or it forces you to add a
considerable amount of code, whose purpose would be only to fool
reference counting, and artificially increase or decrease reference count.
The same applies to your example, if it happens that when creating your
data object you don't know which threads will consume it, because
threads are created dynamically (captors activated and deactivated,
options enabled/disabled, users connecting and disconnecting, etc).
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
