Blake McBride <bl...@mcbride.name> wrote:
|On Thu, Dec 19, 2013 at 8:55 AM, erik quanstrom <quanstro@\
|quanstro.net>wrote:
|
|>> I was thinking about the problem and actually, at least in all
|>> circumstances I can think of, changing that one operation from <= to <
|>> would fix the problem. If the times are on the same second, I would
|>
|> i thought this idea might come up. i think the reason not to do this
|> is a very fundamental principle: correctness. never give up on
|> correctness.
|>
|I for one favor practical usefulness over theoretical correctness. An
I think on FAT filesystems even giving up correctness won't help
you with it's two second resolution.
--steffen
--- Begin Message ---
On Thu, Dec 19, 2013 at 8:55 AM, erik quanstrom <quans...@quanstro.net>wrote:
> > I was thinking about the problem and actually, at least in all
> > circumstances I can think of, changing that one operation from <= to <
> > would fix the problem. If the times are on the same second, I would
> never
> > have had time to change it. This would fix the problem. Perhaps this
> > functionality can be controlled by an environment variable like NPROC.
>
> i thought this idea might come up. i think the reason not to do this
> is a very fundamental principle: correctness. never give up on
> correctness.
>
>
I for one favor practical usefulness over theoretical correctness. An
environment variable option would trivially satisfy both groups. It could
operate as-is so nothing pre-existing would be affected.
Blake
--- End Message ---
