On 09/23/2014 11:31 AM, Giuliano Colla wrote:
Il 23/09/2014 02:24, John Briggs ha scritto:
Sven
At the risk of starting a flame war I have been pondering this question
since these threads have started:
Why has there been so many messages on this list debating the pros
and cons
of reference
---
Mitov Software
www.mitov.com
---
-Original Message- From: John Briggs
Sent: Monday, September 22, 2014 5:24 PM
To: FPC developers' list
Subject: Re: [fpc-devel] weak referencing
On 22/09/14 19:21, Sven Barth wrote:
Am 22.09.2014 17:11 schrieb Jonas Maebe jonas.ma...@elis.ugent.be
mailto:jonas.ma...@elis.ugent.be:
On 22 Sep 2014, at 16:44, Peter Popov wrote:
TRefObject = referenced class(TWhateverBase)
end;
I would strongly recommend against that. Referenced and
Il 23/09/2014 02:24, John Briggs ha scritto:
Sven
At the risk of starting a flame war I have been pondering this question
since these threads have started:
Why has there been so many messages on this list debating the pros and cons
of reference counting objects?
Because many of us are scared
Am 23.09.2014 10:39 schrieb Marco van de Voort mar...@stack.nl:
In our previous episode, Sven Barth said:
Because people want new features. There are Delphi programmers that look
at FPC and think It does not support XYZ, so I won't use it, even if
IMHO a very large percentage of them will
(to Sven)
So the cycle break mechanism is going to be marking potential cycle cases
as weak.
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection itself already too hard?
IOW I'm wondering what will happen (and what to do) if there is a cycle in a
Am 22.09.2014 11:57 schrieb Marco van de Voort mar...@stack.nl:
(to Sven)
So the cycle break mechanism is going to be marking potential cycle cases
as weak.
Basidally, yes.
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection itself already too
Marco van de Voort schrieb:
(to Sven)
So the cycle break mechanism is going to be marking potential cycle cases
as weak.
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection itself already too hard?
IOW I'm wondering what will happen (and what to do)
Am 22.09.2014 14:31 schrieb Hans-Peter Diettrich drdiettri...@aol.com:
Marco van de Voort schrieb:
(to Sven)
So the cycle break mechanism is going to be marking potential cycle cases
as weak.
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection
In our previous episode, Sven Barth said:
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection itself already too hard?
IOW I'm wondering what will happen (and what to do) if there is a cycle
in a
sufficiently complex program.
At least I
In our previous episode, Hans-Peter Diettrich said:
Do you still plan to at least detect cycles for debugging purposes?
Or is the cycle detection itself already too hard?
IOW I'm wondering what will happen (and what to do) if there is a cycle in a
sufficiently complex program.
I
-devel@lists.freepascal.org
Subject: Re: [fpc-devel] weak referencing (was Suggestion:.)
Am 22.09.2014 14:31 schrieb Hans-Peter Diettrich drdiettri...@aol.com:
Marco van de Voort schrieb:
(to Sven)
So the cycle break mechanism is going to be marking potential cycle cases
as weak
On 22 Sep 2014, at 16:44, Peter Popov wrote:
Another comment: If referenced objects all derive from a single
base, then, the user cannot possibly have another hierarchy, which
uses ref. objects. As I mentioned earlier, I do this explicitly for
an object well down my hierarchy. So, it
From: jonas.ma...@elis.ugent.be
To: fpc-devel@lists.freepascal.org
Date: Mon, 22 Sep 2014 17:11:08 +0200
Subject: Re: [fpc-devel] weak referencing (was Suggestion:.)
I would strongly recommend against that. Referenced and unreferenced objects
are completely different beasts with different
Am 22.09.2014 16:45 schrieb Peter Popov ppo...@hotmail.com:
How will referenced objects behave when referenced by a threadvar. This
is an exceptional situation for both dynamic arrays and ansi strings.
There is no need for special handling, afterall a threadvar is (roughly) as
if you had
Am 22.09.2014 17:11 schrieb Jonas Maebe jonas.ma...@elis.ugent.be:
On 22 Sep 2014, at 16:44, Peter Popov wrote:
Another comment: If referenced objects all derive from a single base,
then, the user cannot possibly have another hierarchy, which uses ref.
objects. As I mentioned earlier, I do
Am 22.09.2014 17:33 schrieb Peter Popov ppo...@hotmail.com:
I will add another comment to the race condition issues: they are easily
avoided by a single line assembly atomic inc/dec. It however will not
resolve performance issues where a certain function assigns classes
references left and right
On Mon, Sep 22, 2014 at 07:21:46PM +0200, Sven Barth wrote:
Am 22.09.2014 17:11 schrieb Jonas Maebe jonas.ma...@elis.ugent.be:
On 22 Sep 2014, at 16:44, Peter Popov wrote:
Another comment: If referenced objects all derive from a single base,
then, the user cannot possibly have another
: Monday, September 22, 2014 5:24 PM
To: FPC developers' list
Subject: Re: [fpc-devel] weak referencing (was Suggestion:.)
Why has there been so many messages on this list debating the pros and cons
of reference counting objects?
The beauty of the Pascal language is in its structure ie:
procedures
On 23.09.2014 02:24, John Briggs wrote:
Why has there been so many messages on this list debating the pros and cons
of reference counting objects?
The beauty of the Pascal language is in its structure ie:
procedures,functions,OOP. Why does it need to be a functional programming
language as well
20 matches
Mail list logo
