I'm trying to work around it for 2.2. I'll let you know if there are insurmountable problems. -Dave ----- Original Message ----- From: "Tim Peters" <tim.one@comcast.net> To: "David Abrahams" <david.abrahams@rcn.com> Cc: <python-dev@python.org> Sent: Friday, July 12, 2002 2:01 PM Subject: RE: [Python-Dev] long long configuration > [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? > > I thought you thought there was, else there was no apparent reason for the > "Just addressing" message I replied to. > > BTW, do you need this in 2.2.2 too, or is 2.3 good enough? I didn't change > anything on the 2.2 branch. >
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