Hello,
TUniDataSetSpecificOptions.FOwner must be marked as [Weak] for ARC because it generates a reference cycle.
TUniQuery for example will have RefCount 2 immediately after creation and I need to call DisposeOf to free the object.
And I think the same is for TUniConnectionSpecificOptions.FOwner
Best Regards,
Cristian Peta
[Weak] TUniDataSetSpecificOptions.FOwner
Re: [Weak] TUniDataSetSpecificOptions.FOwner
Hello,
Thank you for the information, we have added an attribute [week] to TUniDataSetSpecificOptions.FOwner and TUniConnectionSpecificOptions, as well as to TUniTransactionSpecificOptions.
Thank you for the information, we have added an attribute [week] to TUniDataSetSpecificOptions.FOwner and TUniConnectionSpecificOptions, as well as to TUniTransactionSpecificOptions.
Re: [Weak] TUniDataSetSpecificOptions.FOwner
Hello,
And a little suggestion.
In my opinion for the future there would be better to use
instead of
When ARC will be introduced to desktop compilers, NEXTGEN would not be there.
Best Regards,
Cristian Peta
And a little suggestion.
In my opinion for the future there would be better to use
Code: Select all
{$IFDEF AUTOREFCOUNT}[weak]{$ENDIF}Code: Select all
{$IFDEF NEXTGEN}[weak]{$ENDIF}Best Regards,
Cristian Peta
Re: [Weak] TUniDataSetSpecificOptions.FOwner
Hello,
Thank you for the information, we know about these defines. There is no difference between their using for the time being. We will replace these defines in the new version.
Thank you for the information, we know about these defines. There is no difference between their using for the time being. We will replace these defines in the new version.