Date: Tue, 12 Dec 2000 14:03:52 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: jhb@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: An opaque refcount type Message-ID: <14902.37560.212440.830262@nomad.yogotech.com> In-Reply-To: <200012122100.QAA53113@khavrinen.lcs.mit.edu> References: <mit.lcs.mail.freebsd-arch/XFMail.001212122450.jhb@FreeBSD.org> <200012122100.QAA53113@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> >an opaque refcount_t type. > > By definition, C typedefs can never be opaque. Only pointers to > incomplete aggregates (i.e., `struct foo *' or `union bar *') are > opaque in C. > > In any event, I think requiring a functional interface to reference > counts is probably a Bad Idea. I disagree. This is a very object oriented thing to do, and it allow you to hide the vulgarities of doing things 'safely' behind the API. On a Sparc a refcount might be 24 bits wide, on the 386/486 it can be safely 32 bits, ia64 64bits, etc... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14902.37560.212440.830262>