By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,434 Members | 1,858 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,434 IT Pros & Developers. It's quick & easy.

Re: A question of programming technique in C

P: n/a
Nick Keighley wrote:
On 4 Nov, 20:24, c...@tiac.net (Richard Harter) wrote:
>>
I am going to throw in one curve ball. Our program will contain
references to created bobbles; we won't know where these are so
they can go stale when we delete bobbles. The code will need to
be able to detect that a reference has gone stale and deal with
it appropriately.

I think your design is broken at this point. This isn't a C
problem you'd have exactly the same issues with C++ despite
it's "machinary".
Why? They could simply use reference counted smart pointers, like
tr1::shared_ptr.

--
Ian Collins
Nov 5 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.