Simon Cozens writes:
> I am in two minds here. I want to have Parrot_... prefices on
> functions even if they're *not* completely necessary /pour
> encourager les autres/. However, I don't want to go the way of
> opening up everything in a public API righht now, because once
> you've exported a symbol for developers to use, you can never take
> it away from them again - whereas if nearly everything's private and
> not exported, you can always open it up later.
Part of "configuration" could be building a #define pile so you can
use foo and bar in the .c files, but they're invisibly translated into
Parrot_ and so on equivalents.
Preprocessing hurts my ass, though, when it comes time to debug.
Nat
