Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #5053 > unrolled thread

My invention that is my scalable reference counting with efficient support for weak references version 1.35 is here..

Started byHorizon68 <horizon@horizon.com>
First post2019-06-27 13:30 -0700
Last post2019-06-27 13:30 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.programming.threads


Contents

  My invention that is my scalable reference counting with efficient support for weak references version 1.35 is here.. Horizon68 <horizon@horizon.com> - 2019-06-27 13:30 -0700

#5053 — My invention that is my scalable reference counting with efficient support for weak references version 1.35 is here..

FromHorizon68 <horizon@horizon.com>
Date2019-06-27 13:30 -0700
SubjectMy invention that is my scalable reference counting with efficient support for weak references version 1.35 is here..
Message-ID<qf390t$arv$6@dont-email.me>
Hello..



My invention that is my scalable reference counting with efficient 
support for weak references version 1.35 is here..

Here i am again, i have just updated my scalable reference counting with 
efficient support for weak references to version 1.35, I have just added 
a TAMInterfacedPersistent that is a scalable reference counted version, 
and now i think i have just made it complete and powerful.

Because I have just read the following web page:

https://www.codeproject.com/Articles/1252175/Fixing-Delphis-Interface-Limitations

But i don't agree with the writting of the guy of the above web page, 
because i think you have to understand the "spirit" of Delphi, here is why:

A component is supposed to be owned and destroyed by something else, 
"typically" a form (and "typically" means in english: in "most" cases, 
and this is the most important thing to understand). In that scenario, 
reference count is not used.

If you pass a component as an interface reference, it would be very 
unfortunate if it was destroyed when the method returns.

Therefore, reference counting in TComponent has been removed.

Also because i have just added TAMInterfacedPersistent to my invention.

To use scalable reference counting with Delphi and FreePascal, just 
replace TInterfacedObject with my TAMInterfacedObject that is the 
scalable reference counted version, and just replace 
TInterfacedPersistent with my TAMInterfacedPersistent that is the 
scalable reference counted version, and you will find both my 
TAMInterfacedObject and my TAMInterfacedPersistent inside the 
AMInterfacedObject.pas file, and to know how to use weak references 
please take a look at the demo that i have included called example.dpr 
and look inside my zip file at the tutorial about weak references, and 
to know how to use delegation take a look at the demo that i have 
included called test_delegation.pas, and take a look inside my zip file 
at the tutorial about delegation that learns you how to use delegation.

I think my Scalable reference counting with efficient support for weak 
references is stable and fast, and it works on both Windows and Linux, 
and my scalable reference counting scales on multicore and NUMA systems,
and you will not find it in C++ or Rust, and i don't think you will find 
it anywhere, and you have to know that this invention of mine solves
the problem of dangling pointers and it solves the problem of memory 
leaks and my scalable reference counting is "scalable".

And please read the readme file inside the zip file that i have just 
extended to make you understand more.

You can download my new scalable reference counting with efficient 
support for weak references version 1.35 from:

https://sites.google.com/site/scalable68/scalable-reference-counting-with-efficient-support-for-weak-references


Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]


Back to top | Article view | comp.programming.threads


csiph-web