[E-devel] Opaque types in C

[Jeff B. <je...@je...>]

On Mon, Feb 12, 2001 at 03:51:29PM -0800, ra...@ra... wrote:
> well from mypoint it is - it makes the type opaque - i can change
> anything inside the type at whim - and typecasting keeps it type safe. i
> think we just disagree on implimentation here - but if you have a better
> way of making a type opaque in C and keeping it typesafe - tell me
> -because i havent seen one.

When I'm coding in C, I kinda like putting something like:

    typedef struct type_s type;

.in the exported header file.  The type_s (_s means struct) is defined either
within the .c or a not-installed header somewhere.  Then outside code can't
modify the contents of the struct and you don't need typecasting.

That's one of the reasons I like C++ though...  just don't get to code in it
very often.

Anyway, sorry to butt in on the heated argument..

Jeff

-- 
Jeff Brubaker - je...@je... - http://jeffro.net/