On 23/02/2015 07:36, Vlad Khorsun wrote: > 22.02.2015 20:11, Adriano dos Santos Fernandes wrote: > >> A solution must be to pass a parameter to destroy methods specifying if >> they should release or not the object. > Must be ? I don't think so. I'm not ready to point to correct solution > right now, but additional parameter is not a solution, as for me. > I prefer to know more opinions... >
Could be, whatever... It's just weird too that with normal pointers one would need to destroy and release. It was clear for me since the start that usage of reference count there, specially for objects with destroy methods were going to be problematic, but you all didn't want to see. We're trying to mix different OO approaches. For example, MS ADO who uses COM and ref. counting has a different way to deal with objects. Some (most, all?) objects start dead, and you need to open them, then you can close them, reopen them, etc. It's just completely different approach than what we have, mixing things (non resurrect objects with ref. counting). Adriano ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
