Undefined calling conventions in Python.h

[Ben Sizer]

On Jul 23, 1:19 pm, Fredrik Lundh <fred... at pythonware.com> wrote:
> Ben Sizer wrote:
> > You should put the extern block around the #include <python.h> call
> > rather than individual functions, as surely the C calling convention
> > should apply to everything within.
>
> Hello?  Python's include files are C++ safe.  I even posted a complete
> compiler session to show that I'm not making that up.
>
> </F>

In theory, yeah. In practice, if his compiler was somehow not
respecting that, then a quicker fix is to enclose the #include than to
do individual prototypes. Admittedly that might obscure the problem
rather than solve it.

--
Ben Sizer