[Python-Dev] #ifdef __cplusplus?
David Cournapeau
cournape at gmail.com
Fri Jan 2 10:41:37 CET 2009
On Fri, Jan 2, 2009 at 4:51 PM, Alexander Belopolsky
<alexander.belopolsky at gmail.com> wrote:
> On Fri, Jan 2, 2009 at 2:26 AM, Adam Olsen <rhamph at gmail.com> wrote:
> ..
>> Compiling as C++ is too obscure of a feature to warrant uglifying the
>> code.
>
> Malloc casts may be hard to defend, but most of python code base
> already has them, there is little to be gained from having these casts
> in some places and not others. There are other design flaws that a
> C++ compiler may help to catch. Two examples that come to mind are
> use of void* where a typed pointer is a better match and declaring
> external functions in .c file instead of including an appropriate
> header. In most cases keeping in mind compliance with C++ leads to
> better design, not to uglier code.
Can't those errors be found simply using appropriate warning flags in
the C compiler ? C has stopped being a subset of C++ a long time ago
David
More information about the Python-Dev
mailing list