Martin v. Löwis wrote: > That future version might get published in 2270,
There are *already* differences which make C and C++ annoyingly incompatible. One is the const char * const * issue that appeared here. Another is that it no longer seems to be permissible to forward-declare static things, which has caused me trouble with Pyrex. That's not just a deprecation -- some compilers refuse to compile it at all. Personally I wouldn't mind about these things, as I currently don't care if I never write another line of C++ in my life. But if e.g. Pyrex-generated code is to interoperate with other people's C++ code, I need to worry about these issues. > when everybody has switched to C++, and compatibility > with C is no longer required. Yeeks, I hope not! The world needs *less* C++, not more... > Sure you can still use stdio, and it is > never going away (it isn't deprecated). However, you > have to spell the header as > > #include <cstdio> > > and then refer to the functions as std::printf, > std::stderr, etc. Which makes it a very different language from C in this area. That's my point. Greg _______________________________________________ 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
