On Sat, Jan 23, 2010 at 10:09:14PM +0100, Cesare Di Mauro wrote: > Introducing C++ is a big step, also. Aside the problems it can bring on some > platforms, it means that C++ can now be used by CPython developers. It > doesn't make sense to force people use C for everything but the JIT part. In > the end, CPython could become a mix of C and C++ code, so a bit more > difficult to understand and manage.
Introducing C++ is a big step, but I disagree that it means C++ should be allowed in the other CPython code. C++ can be problematic on more obscure platforms (certainly when static initialisers are used) and being able to build a python without C++ (no JIT/LLVM) would be a huge benefit, effectively having the option to build an old-style CPython at compile time. (This is why I ased about --without-llvm being able not to link with libstdc++). Regards Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
