[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: parse-duration.c - TIME_MAX conflict
|
From: |
Bruce Korb |
|
Subject: |
Re: parse-duration.c - TIME_MAX conflict |
|
Date: |
Tue, 17 Jun 2014 16:58:31 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9 |
On 06/17/14 09:06, Jonas 'Sortie' Termansen wrote:
It actually turns out that POSIX has reserved the _MIN and _MAX
suffixes for <limits.h> as stated in POSIX 2008 `2.2.2 The Name Space'.
It has a nice table with all the POSIX namespace rules that you can
view online:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02_02
Hmmm. Missed it. Probably wrong search term. Thank you.
They still claim any symbol ending with '_t' and such a claim
weakens the strength of their claim on name spaces.
But since my name is not Don Quixote, I'm not going to try
to push them to make a more modest and targeted name space claims.
- parse-duration.c - TIME_MAX 2038 unpreparedness, Jonas 'Sortie' Termansen, 2014/06/01
- Re: parse-duration.c - TIME_MAX 2038 unpreparedness, Bruce Korb, 2014/06/10
- Re: parse-duration.c - TIME_MAX 2038 unpreparedness, Jim Meyering, 2014/06/10
- Re: parse-duration.c - TIME_MAX 2038 unpreparedness, Jonas 'Sortie' Termansen, 2014/06/11
- Re: parse-duration.c - TIME_MAX 2038 unpreparedness, Jim Meyering, 2014/06/11
- Re: parse-duration.c - TIME_MAX 2038 unpreparedness, Bruce Korb, 2014/06/14
- Re: parse-duration.c - TIME_MAX conflict, Bruce Korb, 2014/06/15
- Re: parse-duration.c - TIME_MAX conflict, Jonas 'Sortie' Termansen, 2014/06/15
- Re: parse-duration.c - TIME_MAX conflict, Jonas 'Sortie' Termansen, 2014/06/17
- Re: parse-duration.c - TIME_MAX conflict,
Bruce Korb <=