Howdy, all. I just fixed another bug in the new dtimep.lex. When Shantonu
wrote the new version, he left out all the #ifdef DSTXXX stuff. Dunno why
-- guess he thought it was some obscure hack that hopefully wasn't
necessary.
Not the case, though. The code controlled by that #define is in charge of
properly interpreting numeric-only timezone offsets in zones that observe
Daylight Saving Time.
For instance, a mail sent to me this morning with this date:
Date: Mon, 24 Jul 2000 09:31:44 -0700
was being printed as:
Date: Mon, 24 Jul 2000 09:31:44 MST
After putting the missing #ifdef DSTXXX stuff back in, it's properly printed
as:
Date: Mon, 24 Jul 2000 09:31:44 PDT
I've also renamed DSTXXX to the rather more descriptive
ADJUST_NUMERIC_ONLY_TZ_OFFSETS_WRT_DST.
I did a little testing, and it appears that more bugs remain in the current
dtimep.lex:
% /usr/local/stow/nmh-1.0.4/bin/scan -form scan.time \
| awk '{print $3}' > 1.0.4
% /usr/local/stow/nmh-1.0.4+dev/bin/scan -form scan.time \
| awk '{print $3}' > 1.0.4+dev
% diff 1.0.4 1.0.4+dev
44,45c44,45
< 21:34+02
< 23:52+02
---
> 21:34+08
> 23:52+08
65c65
< 07:26+02
---
> 07:26+08
74c74
< 09:49+02
---
> 09:49CDT
92c92
< 16:38-00
---
> 16:38BST
117c117
< 23:48PST
---
> 23:48GMT
181c181
< 19:22+02
---
> 19:22+08
198c198
< 09:03GMT
---
> 00:00GMT
I don't think I'll have time to look at these any time super-soon, so if
anyone else could poke around, that'd be great...
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
