Mailman 3 December 1999 - Cplusplus-sig

beginner
by Bill Shui Dec. 22, 1999

Dec. 22, 1999

Hi there, I'm an beginner-intermediate c++ programmer, and I've also been programming in Python for over a year also . I have also read through the mailing list archive. I'm working on a project as a hobbie, it also will help me to gain more appreciation of C/C++ and Python. some friends of mine have written (not 100% completed yet) a DBMS(engine, parser, the lot), and I've been thinking of writing api for it and port it to python. but in order to do that, I'll need a better understanding of Python and C++, I assume. so I was wondering, what are the essentials that I need to know in order to be able to write C++ codes which can be imported by Python and vice versa? Your helps are much appreciated. cheers Bill Shui

2 1

RE: [C++-SIG] Python calling C++ issues
by Dror, Ephi Dec. 3, 1999

Dec. 3, 1999

Hi Mark, Thanks a lot again. We tried it but unfortunately it did not help in our case. Does anyone know where can we download C++ based debug version of Python 1.52 for Linux? Our next step is to use Python 1.52 which is compiled with C++ and possibly a debug version and then try our little sample. Thanks a lot. Ephi. -----Original Message----- From: Mark Hammond [mailto:mhammond@skippinet.com.au] Sent: Wednesday, November 24, 1999 12:53 AM To: 'Ephi Dror'; c++-sig(a)python.org Subject: RE: [C++-SIG] Python calling C++ issues > Unfortunately, we don't seems to understand what do you mean > by "Object". Is > it something we need to define or is it already defined in a > h file that we > forgot to include. We use Linux/gcc environment. Sorry - I meant "PyObject" > Also, in our sample, we did not use virtual function Hmmm - OK - my advice could well be wrong. Unless your C compiler always adds a vfptr. I have seen this problem (when using virtuals) before and the symptoms sound almost identical. Try the code snippet I posted, and see if the debugger does show the "PyObject *" and the "Spam *" as different values, even though they are pointing to the same object. Otherwise Im afraid I have no idea... Mark. _______________________________________________ C++-SIG maillist - C++-SIG(a)python.org http://www.python.org/mailman/listinfo/c++-sig

12 29

Re: [C++-SIG] Python calling C++ issues
by Dirk Heise Dec. 2, 1999

Dec. 2, 1999

> Von: Guido van Rossum <guido(a)CNRI.Reston.VA.US> > An: c++-sig(a)python.org > Betreff: Re: [C++-SIG] Python calling C++ issues > Datum: Donnerstag, 2. Dezember 1999 16:31 > > All I can say is, the more I hear about C++, the less likely it > becomes that Python 2.0 will be written in it. Come on! You don't have to use all sick features they built into the standard. During my dull C++-9-to-5 job, i avoid operator overloading, C++ references, "const" whereever possible, STL and hell-knows-what and i'm having a great time as a C++-10-percenter. Possibly not Geoffreys opinion, but it pays the rent :-) But one serious question: Do you consider prototyping Python 2 in Python 1? Dirk

1 0

Re: Python calling C++ issues
by Greg Couch Dec. 2, 1999

Dec. 2, 1999

Guido van Rossum <guido(a)CNRI.Reston.VA.US>: > Rant aside, what compiler is going to support different datatype sizes > for stuff declared extern "C" than for native C++ types? Get real. My understanding is that the issue usually isn't datatype sizes, it's the calling convention. The ABI for C++ functions may be different than for C functions. extern "C" gives that the C++ compiler that clue. Clueless compilers require extension keywords, such as __cdecl, for similar effects. Greg Couch gregc(a)cgl.ucsf.edu (c++-sig digest reader)

1 0