> On May 8, 2021, at 7:59 AM, Sven Barth via fpc-devel
> It has the exact same problems that my branch had (especially the interaction
> of reference counted instances with non-reference counted ones).
> Using a variable/parameter/field based approach (like the idea with
> On May 8, 2021, at 8:05 AM, Sven Barth wrote:
>> a := TArray.Create([1,2,3]).AutoRelease;
>> We can't do this in Pascal because the AutoRelease functions return type is
>> not compatible with the type of the caller. Could we add something like an
>> "Any" return type to Pascal which
Am 22.04.2021 um 17:52 schrieb Ryan Joseph via fpc-devel:
On Apr 16, 2021, at 11:35 AM, Ryan Joseph wrote:
Got this all integrated and put up the changes to
https://bugs.freepascal.org/view.php?id=35261. Now I'm waiting for another
final review. :)
The next thing to do now is to handle a
Am 08.05.2021 um 18:23 schrieb Ryan Joseph via fpc-devel:
On May 8, 2021, at 7:59 AM, Sven Barth via fpc-devel
It has the exact same problems that my branch had (especially the interaction
of reference counted instances with non-reference counted ones).
Am 06.05.2021 um 17:33 schrieb Ryan Joseph via fpc-devel:
I found something sneaky I'd like to confirm before I decide what to do about
1) "T" in TAnyClass is specialized as Integer from the first parameter with
TSomeClass (which is TAnyClass).
2) "U" is getting specialized as String by
> On May 8, 2021, at 11:18 AM, Sven Barth wrote:
> It's not about reference counted classes vs. managed records, but about
> whether it's *per type* or *per variable*, the implementation details are
> completely irrelevant for now.
So the biggest concern you see if that classes are easier
> On May 8, 2021, at 12:04 PM, Sven Barth wrote:
> You need to use ChangeOwner as well, but as I wrote you need to pay attention
> for which created symbol you do it at what time.
Ok, maybe this is what I got wrong didn't use ChangeOwner. When you say "add
to" what exactly do you mean?
On 07/05/2021 07:26, Sven Barth via fpc-devel wrote:
> Trunk also supports POSIX exceptions on selected *nix based systems,
> though I haven't looked in depth yet in how far they incur a runtime
> penalty (also they need to be enabled by enabling them in the compiler
> and then recompiling
On 07/05/2021 18:41, Ryan Joseph via fpc-devel wrote:
> Does that mean if you disable implicit exceptions then ALL ref counted types
> leak memory?
Only if an exception occurs.
fpc-devel maillist - email@example.com
Am 07.05.2021 um 23:16 schrieb Ryan Joseph via fpc-devel:
On May 7, 2021, at 2:52 PM, Sven Barth wrote:
As said the main problem of reference counting on object instances, especially
if enabled by default like the Delphi NextGen compiler did, will lead to
problems in *existing* code and
Am 07.05.2021 um 17:40 schrieb Benito van der Zander via fpc-devel:
The introduction of generics and their abundant use in Delphi has
noticably slowed down the compiler and increased binary sizes. To my
dismay, compile times of 20 seconds up to 2 minutes have become not
uncommon in Delphi.
Am 07.05.2021 um 17:57 schrieb Ryan Joseph via fpc-devel:
On May 7, 2021, at 2:46 AM, Sven Barth via fpc-devel
I cannot speak for others, but I think 90% of potential use cases for ref
would be covered like this in my code: objects that only live inside a
Mail list logo