* equality time test in source and object code check
@ 2010-04-14 19:40 stefan
2010-04-14 21:06 ` Andy Wingo
0 siblings, 1 reply; 2+ messages in thread
From: stefan @ 2010-04-14 19:40 UTC (permalink / raw)
To: bug-guile
Hi,
I'm not certain if this is a Bug. But it looks like there is an
equality test of times for the check if the object file is in sync with
the source file. I could imagine that the rule that has to be obeyed is
obj-code-file-time >= source-code-time
testing for equality looks a little scary to me
/Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: equality time test in source and object code check
2010-04-14 19:40 equality time test in source and object code check stefan
@ 2010-04-14 21:06 ` Andy Wingo
0 siblings, 0 replies; 2+ messages in thread
From: Andy Wingo @ 2010-04-14 21:06 UTC (permalink / raw)
To: stefan; +Cc: bug-guile
On Wed 14 Apr 2010 21:40, stefan <stefan.tampe@spray.se> writes:
> I'm not certain if this is a Bug. But it looks like there is an
> equality test of times for the check if the object file is in sync with
> the source file. I could imagine that the rule that has to be obeyed is
>
> obj-code-file-time >= source-code-time
>
> testing for equality looks a little scary to me
That test won't work normally, because often when installing debs or
rpms, the file timestamps come from the rpm and not the time of
installation.
So, we check timestamp equality. Perhaps we should use an epsilon, but
OTOH guile should be able to timestamp files as precisely as the
filesystem supports, including nanosecond resolutions, so perhaps this
won't be a problem.
Or, perhaps this is wishful thinking :)
A
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-14 21:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-14 19:40 equality time test in source and object code check stefan
2010-04-14 21:06 ` Andy Wingo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).