[C++-SIG] Python calling C++ issues

[Guido van Rossum]

> Geoffrey Furnish writes:
> > 
> > "Hasn't failed yet" is not the same as "works because it is intended
> > to work".  The right way to hold pointer values, is in objects of
> > pointer type.

David Beazley <beazley at cs.uchicago.edu>:

> <rant>
> Yeah, yeah, whatever.  For all of the time that C++ facists spend
> whining about "intended behavior" and the "right" way to do things, I
> have yet to see a compiler with 13 bit integers, 77 bit longs, and 125
> bit pointers, nor do I ever think I will see such a thing in my
> lifetime.  Therefore, semantics aside, there is really nothing wrong
> with opting for a simple approach if it works and you know what you
> are doing.  Otherwise, I just don't see the point of needlessly making
> things 10 times more complicated than it has to be.
> </rant>

Rant aside, what compiler is going to support different datatype sizes
for stuff declared extern "C" than for native C++ types?  Get real.

--Guido van Rossum (home page: http://www.python.org/~guido/)