This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Changes the default size of time_t to 64 bit.




On 8/11/2017 3:58 PM, Hans-Bernhard Bröker wrote:
Am 11.08.2017 um 22:15 schrieb Jeff Johnston:

What about: --enable-time_t-compat to indicate it is a compat-type option
indicating old behaviour?

That would violate rule-for-naming-things #1: never distinguish between
two stages of development of something by naming one of them "new", or
the other one "old".  If you do, you'll end up having to explain what
the difference between really-very-new and
brand-spanking-really-very-new actually is, and having no idea how to do
that.

+1 RTEMS still has a directory named "new-exceptions" which is now probably
fifteen years old. :(
IMHO, the name of that option absolutely has to contain explicit mention
of "32 bits", because its entire reason to exist is to make time_t 32
bits.  Whether the actual time_t typedef then ends up being int, long,
int_least32_t or what-not is of no interested to the person using that
option, so has no business appearing in the option name.

The only alternative option syntax I might find acceptable would be
something like --enable-time_t_override=<typename>, but only if
configure can be taught to check that <typename> is actually a viable
choice.


I lean to making it clear you are forcing 32 or 64 bits.

--joel
RTEMS


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]