On Tuesday 13 October 2009 21:10, Bernhard Reutner-Fischer wrote: > >We can explicitly use uint32_t there if you are concerned we'll > >ever get arches with sizeof(int) > 4. > > I'd go for time_t, just because i'm paranoid.
Paranoid scenario is: you update resolv.conf exactly 2^N seconds after it was last updated, and oh no, uclibc does not notice that. N here is bit width of the variable. I'd use uint32_t. 2^32 secs = 136 years. > May i ask you to apply such a thing (with whatever type you think is > safe)? TIA! Done. -- vda _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
