> What's the plan for removing this stuff again when UnixWare fixes > their bugs? There is no plan for that at the moment. Please have a look at http://sourceforge.net/tracker/?group_id=5470&atid=305470&func=detail&aid=450710 for prior discussion on the matter; the submitter has considered coming up with an autoconf bug test for the problem, but hasn't followed up with that - testing for the system apparently turned out to be the easier route. One possible approach is that UnixWare releases are regularly tested for the presence of the bug. That would be simplified if the nature of the problem was documented somewhere, that also hasn't happened. To retest, it might be easiest to disable the SCO_ macros, and re-run the test suite; test_math will fail if the bug is still present. Once the version of UnixWare is identified that first fixed the bugs, it hopefully is possible to check the value of __SCO_VERSION__ to tell apart the good, the bad, and the ugly. Regards, Martin
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