--=-R+GGiPN+KuS6g7PcEhlL Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > Could you please call it __EXTENSIONS__? Many of the functions that > fall under it are not BSD specific, and _BSD_SOURCE selects the > favour-bsd API on other systems.=20 The responsible person seems to be against a solution like this. But, in the discussion it turns out that you are right and there some bugs in FreeBSD's unistd.h. The fixes will (probably) committed today. But=20 there are some issues left mostly in the RPC and socket code, which need __BSD_VISIBLE. Some problems are left, because some functions (like ftello) are only defined at a higher POSIX level. =20 > out support for a number of such systems. It's just not worth the > pain. Python works on Posix systems, and uses extensions where > available. It does not work on strange systems; tough luck for users > of such systems (we have yet to hear from a DYNIX user who wants to > run Python 2.2). I'm not talking about strange systems. Although I've not tested it BSD/OS comes to mind or NetBSD/OpenBSD.=20 > > > Only if all other options have been exhausted. What problems occur if > > > _XOPEN_SOURCE is defined? > > _XOPEN_SOURCE sets _POSIX_C_SOURCE. >=20 > And why is that a problem? In that case __BSD_VISIBLE is not set. Regards, Marc --=20 "Premature optimization is the root of all evil." -- Donald E. Knuth --=-R+GGiPN+KuS6g7PcEhlL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA9z+O+7YQCetAaG3MRAgQfAJ9bFfnsCsua/VCrJwUUsL+Ysw7v5gCggav9 B7m5cmBNKED5UK+uGarc0Kg= =Fyum -----END PGP SIGNATURE----- --=-R+GGiPN+KuS6g7PcEhlL--
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