Well what we are doing currently is if the mtime is not exactly what it was before then assume it is changed. I don't bother doing greater than checking just if it is different. Rails currently just checks if the file is > than the last compile time (which like you said can get messed up). I think doing exact mtime checking gets around most issues. If we need to we can eventually add size too, but I just went for simple (and that was what rails was doing too).
<br><br><div><span class="gmail_quote">On 6/18/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><div dir="ltr" align="left"> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span><span>A thought: timestamps
can in general be kind of flakey, esp. when doing things like FTP xfr's
between machines (?and version control checkouts?). And
you really don't wanna hear me whine about daylight savings changes on
windows... Maybe shouldn't be the sole criteria for template change
detection. How about adding a size-changed condition as
well?</span></span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span></span></font> <br></div></div></div></blockquote></div><br>