Re: copy constructor for sockets

[Matthew Heaney <matthewjheaney@earthlink.net>]

"Marius Amado Alves" <amado.alves@netcabo.pt> writes:

> > ... during Adjust you increment the refcount of the socket.  You
> > decrement the refcount during Finalize.
> 
> Right. Now you only have to know how many times Finalize gets called,

Why?  When the refcount goes to zero, then the last of the socket
objects attached to that handle have been finalized, and you can
deallocate handle.  What's the problem?


> where from,

Why?  The whole point of using reference counting is to be able to
ignore when and by whom, because it is the socket object itself that
controls when the handle is closed.


> in which of these times you should decrement,

Huh?  Every time, of course.  How could it be otherwise?  What would a
reference counting scheme even mean, if you didn't decrement the
refcount during finalization of the object?


> and declare all sockets at library level.

Huh?  The sockets package is declared at library level, but socket
objects can be declared anywhere, at any level.


> A nice Rube Goldberg machine. Don't you just love the Ada way?

I'm not sure what you mean by "Ada way."  The code I described in my
last post was pseudo-code, translated from C++ code.  The reference
counting scheme I described is the same in either language.