> > 2) timezone/localtime.c, transtime() has a const arcument in the 
> > implementation but non-const in declaration.
> I did this the other way (make implementation match declaration).
> I think the coding was in fact correct per spec, because 
> const-ness of an argument value is not part of the function signature.


> > I'm also seeing a lot of signed/unsigned mismatch, but IIRC it was 
> > said at some point that we don't care about those.
> In HEAD?  They're all cleaned up according to the compilers I use.

More digging then I guess. Probably a #define that's messe dup


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


Reply via email to