> OK, you two, Andy/JF convinced me to OOing also in standard C ;;;)))
Tres bon ;-)
--
Andy Armstrong, Tagish
>> >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 wer
GOMEZ Henri wrote:
>
> >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 constructio
Andy Armstrong wrote:
>
> GOMEZ Henri wrote:
> >
> > >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.
> >
GOMEZ Henri wrote:
>
> >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 constructio
>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 stric
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.
GOMEZ Henri wrote:
>
> We found many definitions like this
> in mod_jk :
>
>
We found many definitions like this
in mod_jk :
xxx.h
struct jk_map;
typedef struct jk_map jk_map_t;
xxx.c
struct jk_map {
jk_pool_t p;
jk_pool_atom_t buf[SMALL_POOL_SIZE];
char **names;
void **values;
unsigned capacity;
unsigned size;
};
Why not having it directly
