Guido van Rossum <guido@python.org> writes:
> > However, I note that Boost.Python has to #include <patchlevel.h> because
> > we have to apply workarounds before #including <Python.h> for certain
> > versions of Python, so I wouldn't say that it's very unrealistic to thi=
nk
> > applications might need these files separately.
>=20
> But this works fine without the protection; probably because
> patchlevel.h contains no C code, only preprocessor stuff.
Certainly (though PP stuff can cause problems too). I'm just saying
that I if you intentionally avoid #include guards on the basis that
it's going to help you find your own bugs/inefficiencies, as Fran=E7ois
seems to be suggesting, you may be unneccessarily limiting
interoperability, which I think is Python's higher goal.
--=20
David Abrahams * Boost Consulting
dave@boost-consulting.com * http://www.boost-consulting.com
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