Re: Embedding vs. extending interface types

[Gordon Henriksen]

On Saturday, January 24, 2004, at 02:28 , Leopold Toetsch wrote:

Mattia Barbon <[EMAIL PROTECTED]> wrote:

I feel I'm becoming annoying, but: the embedding and extending 
interfaces are still using different names for 
Parrot_Interp/Parrot_INTERP. Which one is correct?
AFAIK both. Embedding and extending are to different APIs. The former 
has access to internals the latter doesn't. So they get different types 
for e.g. the interpreter.
All embedders see is this:

        /* include/parrot/interpreter.h */
        struct Parrot_Interp;
        typedef struct Parrot_Interp *Parrot_Interp;
i.e., struct Parrot_Interp is declared, but never defined. So the extra 
Parrot_INTERP type is just cruft. Also, it's not used anywhere in the 
source tree except in extend.h and extend.c.

And does anyone ever use the Interp type from below?

        /* include/parrot/interpreter.h */
        typedef struct Parrot_Interp {
                ...
        } Interp;
—

Gordon Henriksen
[EMAIL PROTECTED]