<div dir="ltr"><div><div><div><div>We started out life with 16 "reserved" bytes in binary files; one of those was appropriated for the compiler version number so we're now at...<br></div> char tzh_version[1];<br>
</div> char tzh_reserved[15];<br></div>Adding something such as "2013e" wouldn't exhaust the reserved bytes; it would complicate regression testing (though not unduly).<br><br></div><div> --ado<br></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 9, 2013 at 2:21 AM, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One other thing. It's been privately suggested to me,<br>
more than once, that a tz binary file should have<br>
a version number in it, identifying which version of<br>
the tz data it came from. Presumably this could be<br>
a new option to 'zic', used by Makefile, e.g.,<br>
<br>
zic -V "$(VERSION)" ...<br>
<br>
would copy the value of VERSION into the zic output file.<br>
<br>
Do you think this is a good idea? If so, where would<br>
be a good place to put the version information -- a<br>
new "version=2013e" line after the POSIX TZ string?<br>
If we are bumping from version '2' to 'version '3'<br>
anyway, now may be a good time to add this, if it's<br>
a good idea to add it that is.<br>
</blockquote></div><br></div>