Guido> If all OO languages were the more or less equivalent except
Guido> for minor syntactic issues, this would be a reqsonable
Guido> assumption. However, as it is, this would make the OO model
Guido> of the wrapper basically the same as that of the language it
Guido> is wrapping. I don't think you would want Python's OO
Guido> mechanisms too tightly bound to those of C++.
Definitely not!! But I'm not sure how tight this bound has to be. If
you want to support everything you are probably in for trouble but
normally even C interfaces are very restricted in just allowing
passing of basic types between the sides (Sorry for not checking this
with Python :-).
Guido> But the true reason why Python isn't based on C++ is of
Guido> course availability.
Guido> There's no reason why some extension modules of Python
Guido> couldn't be written using C++, but of course this isn't the
Guido> same as what you proposed.
Hmm... Well that's interesting (and maybe obvious). I guess I'd better
check how this works with Python before boring you to death on this
subject since this mailing list really is about Python :-)
"It is easier to fight for principles than to live up to them."
-- Alfred Adler