Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +serhiy.storchaka
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 3.2 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
___
Python-bugs-list
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-01-05 22:06, Alexander Belopolsky wrote:
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
Given that you can build Python as library on Unix and as DLL on
Windows, there doesn't appear to be any need to
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Mon, Jan 5, 2009 at 11:43 AM, Marc-Andre Lemburg
rep...@bugs.python.org wrote:
..
GCC doesn't appear to do so, but there's no guarantee that other
C++ compilers won't touch these symbols:
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-01-03 04:38, Alexander Belopolsky wrote:
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Fri, Jan 2, 2009 at 10:54 AM, Marc-Andre Lemburg
rep...@bugs.python.org wrote:
Marc-Andre Lemburg
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-01-05 13:03, Marc-Andre Lemburg wrote:
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-01-03 04:38, Alexander Belopolsky wrote:
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Fri, Jan
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-01-05 19:55, Alexander Belopolsky wrote:
The allocs counters (tuple_zero_allocs, fast_tuple_allocs,
quick_int_allocs, quick_neg_int_allocs) present a case where it is
really hard to justify a change that is only motivated by C++
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Mon, Jan 5, 2009 at 2:58 PM, Marc-Andre Lemburg
rep...@bugs.python.org wrote:
..
For completeness, all exported symbols in Python should have a _Py_
prefix, even if they only get exported in certain debug builds.
I
Marc-Andre Lemburg m...@egenix.com added the comment:
Moving declarations into header files is not really in line with the way
Python developers use header files:
We usually only put code into header files that is meant for public use.
Buy putting declarations into the header files without
Marc-Andre Lemburg m...@egenix.com added the comment:
Also note that by removing the extern C declarations, you not only
change the exported symbol names of functions, but also those of
exported globals.
Those would also have to get declared in the header files, to prevent
their names from
Marc-Andre Lemburg m...@egenix.com added the comment:
The added type casts are useful to have - even outside the context of
the idea behind the patch.
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Fri, Jan 2, 2009 at 10:54 AM, Marc-Andre Lemburg
rep...@bugs.python.org wrote:
Marc-Andre Lemburg m...@egenix.com added the comment:
Also note that by removing the extern C declarations, you not only
change the
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
Added file: http://bugs.python.org/file12560/c++-patch-2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
Removed file: http://bugs.python.org/file12530/c++-patch-1.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4805
___
New submission from Alexander Belopolsky belopol...@users.sourceforge.net:
I am posting this patch mainly to support python-dev discussion on this
topic. In the past (see r45330) it was possible to compile python core
and standard library modules using a C++ compiler.
According to Martin v.
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
A related question discussed on python-dev is whether extern C {}
wrappers should ever be used in .c files. I argue that the answer is no
even if C++ compilability is desired.
The new patch eliminates several uses of
18 matches
Mail list logo
