Re: Demo: Modelling Cost of Travel Paths Between Towns

"Laconic2" <laconic2_at_comcast.net>...
<snip>

> Let's say that we are given two times, and asked whether they are equal
> or
> not.
>
> Here are the two times:
>
> 2004.11.11 24:00
> 2004.11.12 00:00
No, this is two represetations of the same (point in) time. You are mixing "value" and "representation"

> Now a naive comparator would answer the question "no".
Yes, would be naive, since the value is the same ...

> But a comparator
> that really understands what we are talking about
> might take a closer look, and come up with the answer: "yes". I like
> the
> answer "yes", myself, better.
You are not alone <g>

> In fact, I would like the "time type engine" whenever it's done some
> calculation on time, (like adding an "interval" to a "base time") to
> perform one final step, before delivering the result to the outside
> world.
But it is not the job of the "type engine" to deliver the result as a representation to the outside world. It delivers a value. You are mixing ....

> If a computation happened to result in 2004.11.11 24:00, I would want it
> to
> convert it to 2004.11.12 00:00. And I would call this final step
> "normalizing the result".
Ok, in fact "normalizing the representation", but let's not keep nit-picking...

> Once the results of a computation have been "normalized" , a naive
> comparator
> can test for equality by just comparing the representations. Right?
Yes. Received on Fri Nov 12 2004 - 16:33:20 CET