Re: Using delete() instead of release()

Hey,

        Wrote a short one

http://blog.parthenoncomputing.com/xerces/archives/2005/05/memory_manageme.html

Please give comments. This comes up now and again so its worth spending 
a bit of time on to make it understandable.
Gareth


Jason E. Stewart wrote:
> Radovan Chytracek <radovan.chytracek@xxxxxxxxx> writes:
>
>
> > I do not know details of Perl binding for Xerces-C but I think the
> > DOM document could be exposed via a handle in form of smart pointer
> > which can call transparently the release() method in its destructor.
> > Some sort of handle-body design pattern might do it well for this
> > purpose, e.g. BOOST shared_ptr<T> for example.
> Hi Radovan,
>
> I'm really looking to understand the consequences of release() versus
> delete() first. After that I can work on the implementation.
>
> Is calling delete good enough? Or is it critical to call release()?
>
> Cheers,
> jas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: c-dev-help@xxxxxxxxxxxxxxxxx
--
Gareth Reakes, Managing Director      Parthenon Computing
+44-1865-811184                  http://www.parthcomp.com