From: "Tim Peters" <tim.one@comcast.net> > [David Abrahams] > > Just addressing the <0.1 wink> you left out: even if I get the include > > order "right", my users are still screwed if they don't do it the > > same way. > > Give them a pythonboost.h instead that contains the includes in the right > order, or make your boost.h smarter, or ... You fixed the LONGLONG_MAX stuff already, so I don't think there's anything to discuss here, is there? None of my code is confused by HAVE_LONG_LONG. -Dave
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