At 8:57 AM +0100 1/25/04, Mattia Barbon wrote:
Il Sat, 24 Jan 2004 19:42:20 -0500 Gordon Henriksen
<[EMAIL PROTECTED]> ha scritto:
On Saturday, January 24, 2004, at 11:28 , Mattia Barbon 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?
Mattia,
Both are correct. Sort of. :) Parrot_INTERP is an opaque type,
which is
a technique for improving binary compatibility. In the core, which
is
I know that. The problem, as you note in your next mail, is:
Parrot_Interp already has opacity guards, and _is used as an opaque
type in embedding interface_. Now having two parts of the _external_
interface use differently-named opaque types for the same thing
seems pointless, if not confusing.
And pointless. Let's just rename it to Parrot_Interp everywhere.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
