Paul Eggert wrote: > I thought that since some of the other tests already use static_assert, > these tests could do so too.
The difference is: If one of the other static_assert invocations fails and leads to a compilation error, we can and will fix it as soon as it gets reported. Whereas when a platform limits off_t or time_t to 'int' range, there's nothing we can do to fix it. Thus it will be a problem (with this platform) that stays forever. > It's obviously no big deal to revert to dynamic checking and I installed > the attached. Thanks. Bruno
