> Dear lord why? So people can develop extensions using C++? Its > not worth the pain inflicted on everyone else. Let them > recompile with LINKCC=CXX. > > Linking with CXX opens a huge can of stinky worms. First of all, > just because configure found a value for CXX doesn't mean it > works. Even if it does that doesn't mean that using it is a good > idea. Linking with CXX will bring in the C++ runtime. There are > a large number of platforms where the C++ ABI has not been > standarized; for example, anything that used g++. > > Can we please leave LINKCC default to CXX? Its easy enough for > the crazies to override if they like. I'll even create a > configure option for them. Arg. My bad. I did this as an experiment; it didn't break on my machine, but I didn't intend this to become the standard! Thanks for changing it back. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4