RetroSearch Browse

Tue Jun 29 14:03:31 EDT 2004 · https://mail.python.org/pipermail/python-dev/2004-June/045738.html

Paul Sheer <p at 2038bug.com> writes:

>> Neil Hodgson:
>>    I think it is unlikely that such a large patch and resulting C++
>> compatibility policy will be accepted.
>
>
>> Paul Svensson:
>> 
>> The Pythin sorces are written in C; that they fail to compile
>> when usung a compiler for a different language is a feature, not a bug.
>> 
>
> of course :-)
>
> however, most of the changes are good coding practice in any case.
>
> the rest are outright inconsistencies in the python source
> and ought to be fixed -
>
> for instance, the macros 'PyMODINIT_FUNC' and 'staticforward'
> are *not* used with consistency

Isn't staticforward a work around for broken compilers?  I'm not sure
how much brokeness in the compiler we want to live with.

Cheers,
mwh

-- 
  M-x psych[TAB][RETURN]
                                                             -- try it

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045738.html below:

[Python-Dev] Compiling the Python sources with a C++ compiler (aCC)