|
From: | Bruce Korb |
Subject: | Re: parse-duration.c - TIME_MAX conflict |
Date: | Sun, 15 Jun 2014 09:53:46 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9 |
On 06/14/14 14:37, Bruce Korb wrote:
On 06/11/14 15:46, Jim Meyering wrote:I wrote the patch, and tested by running this: ./gnulib-tool --create-testdir --dir=/tmp/x --with-tests --test parse-durationExcellent. Please push it, thank you!
Actually, it occurs to me that the result still uses TIME_MAX and, if not guarded, still conflicts with glibc's claim to a new name. I still think that "implementations" need an unambiguously distinct name space. *_MAX is too greedy.
9999-current.diff
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |