| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Defect in XSH asctime() |
| From: | Larry Dwyer <yyyyyyyyyyy@xxxxxx> |
| Date: | Sun, 14 Dec 2003 22:39:39 -0800 |
| References: | <200312120217.CAA12802@xxxxxx><200312120217.CAA12802@xxxxxx> |
Is there such a thing as year 0? I thought the calendar starts with year 1.
Cheers,
Larry
At 11:19 PM 12/13/2003, Paul Eggert wrote:
At Fri, 12 Dec 2003 02:17:59 GMT, yyyyyyyyyyyyyyy@xxxxxxx writes: > (see <time.h>), and the calculated year does not exceed four digits: > > page 121 line 4428 section asctime() objection > After line 4428, add: > Otherwise, if any of the fields of the tm structure pointed to by > timeptr contain values that are outside the normal ranges, asctime() > behavior is undefined. If the calculated year exceeds four digits, The proposed rewording addresses only the issue where the calculated year exceeds 9999. The specification also address the issue where the calculated year is negative. So I would change "the calculated year does not exceed four digits" to "the calculated year is in the range 0 through 9999 inclusive", and similarly for the other (negated) occurrence of the wording. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Defect in XSH asctime(), Paul Eggert |
|---|---|
| Next by Date: | Re: Defect in XSH asctime(), Jim Zepeda |
| Previous by Thread: | Re: Defect in XSH asctime(), Paul Eggert |
| Next by Thread: | Re: Defect in XSH asctime(), Jim Zepeda |
| Indexes: | [Date] [Thread] [All Lists] |