On 31.05.2013 06:57, Daniel Shahaf wrote: > Branko Čibej wrote on Thu, May 30, 2013 at 22:40:11 +0200: >> On 30.05.2013 21:59, Johan Corveleyn wrote: >>> Running gen-make.py on trunk@1487954, I get the following warning at the >>> end: >>> >>> [[[ >>> WARNING: errno intersects APR error codes: set([10000, 10004, 10009, >>> 10013, 10014, 10022, 10024, 10035, 10036, 10037, 10038, 10039, 10040, >>> 10041, 10042, 10043, 10044, 10045, 10046, 10047, 10048, 10049, 10050, >>> 10051, 10052, 10053, 10054, 10055, 10056, 10057, 10058, 10059, 10060, >>> 10061, 10062, 10063, 10064, 10065, 10066]) >>> ]]] >>> >>> I have not seen this before. Is this something new? Anyone else seeing this? >> I wouldn't be surprised if that was the case on Windows, however, APR >> does not map its error codes from errno but from Win32 status codes. So >> I suspect this is a red herring and a side effect of the symbolic error >> code printout thing. > Yes it's related to the symbolic error names. Those codes have 2 names > - one in Python's errno.errorcode[] and one in apr_errno.h. > >> Very likely, the mapping generator is just a wee bit too Unix-centric. > Thanks for assuming my code is buggy without reading it. The logic in > question is platform-agnostic.
Sorry, that's not what I meant -- I meant specifically the bit that prints that warning, which maybe shouldn't be quite so platform-agnostic. -- Brane
