RE: [J-T-C] struct defs

[GOMEZ Henri]

>The reason would be to keep the implementation details of the structure
>private so that people aren't tempted to access the fields 
>directly. All
>the caller gets is an opaque handle. Think of it as 'objects lite' for
>C.

I could understand the OO construction if we were using C++
but in strict K&R when you need to have access elements in 
a struct you need to know about them ?)

The goal is to have functions defs in .c and data defs in .h
preparing scandoc task

So what about that repartition ?