<br><br><div class="gmail_quote">On Mon, Oct 27, 2008 at 12:32 PM, Olson, Arthur David (NIH/NCI) [E] <span dir="ltr"><<a href="mailto:olsona@dc37a.nci.nih.gov">olsona@dc37a.nci.nih.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm forwarding this message from hsv, who is not on the time zone<br>
mailing list. Those of you who are on the list, please direct replies<br>
appropriately.<br>
<br>
--ado<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:hsv@tbbs.net">hsv@tbbs.net</a> [mailto:<a href="mailto:hsv@tbbs.net">hsv@tbbs.net</a>]<br>
Sent: Monday, October 27, 2008 3:01<br>
To: <a href="mailto:tz@lecserver.nci.nih.gov">tz@lecserver.nci.nih.gov</a><br>
Subject: file-format<br>
<br>
The man-page describes a fairly loose fileformat, but the actual files<br>
show less looseness: there is no quoted sharp (#), all one name s Rules<br>
are in a bunch in time order, with no other Rule or Zone in between, all<br>
weekday-names are three-letter-long abbreviations of capital letter and<br>
twain small letters. Can I afford to count on that, or is it really<br>
needful to parse a much looser-formatted file than really is there?<br>
</blockquote></div><br><br>It depends on whether you are willing to risk your code breaking at an unspecified time in the future when the rules you see in action - as opposed to those documented - are suddenly but legitimately altered (remaining as documented). If you can afford to take the risk, you can parse to the stricter rules you see in use. If you cannot afford to take the risk, you should follow the documentation.<br clear="all">
<br>-- <br>Jonathan Leffler <<a href="mailto:jonathan.leffler@gmail.com">jonathan.leffler@gmail.com</a>> #include <disclaimer.h><br>Guardian of DBD::Informix - v2008.0513 - <a href="http://dbi.perl.org">http://dbi.perl.org</a><br>
"Blessed are we who can laugh at ourselves, for we shall never cease to be amused."<br>