Although TBH what i'd prefer more than the above is language features that would allow me to implement refcounted objects myself. Stuff like automatic destruction when a generic variable goes out of scope, etc.
On Mon, Sep 22, 2014 at 5:45 PM, Kostas Michalopoulos < badsectorac...@gmail.com> wrote: > I prefer the TARCObject approach too, i don't want anything to be > refcounted unless i *explicitly* ask for it (yes i know some things are > already refcounted and at the past i was bitten by that which is a big > reason why i don't want hidden things to do magic stuff behind my back). > Also i don' want a useless field in TObject (like a refcount field), object > instances are already too big IMO. > > On Mon, Sep 22, 2014 at 3:03 PM, Michael Schnell <mschn...@lumino.de> > wrote: > >> On 09/22/2014 02:05 PM, Hans-Peter Diettrich wrote: >> >>> TMyARCclass = interface(TObject) >>> >> IMHO, Sven's idea of introducing a "TARCObject" base class (triggering >> the compiler magic for ref counting) sounds a lot nicer. >> >> -Michael >> >> _______________________________________________ >> fpc-devel maillist - fpc-devel@lists.freepascal.org >> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel >> > >
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
