<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
> If you use integer counts of some small interval, that small interval<BR>> is what I mean has to be specified somewhere.<BR><BR>
<BR>
There would be one and only interval for all time measurements.<BR>
=> Whatever NT uses. 10s of nanoseconds I believe.<BR>
Isn't that similar to saying you have to specify it is seconds?<BR>
Or seconds is easier to remember and understand?<BR>
NT's unit is a little difficult for me, granted.<BR>
<BR>
<BR>
> There's nothing much wrong with floating point. It works fine and Time.T<BR>> can certainly represent intervals much smaller than a second using any<BR>> reasonable epoch (almost the age of the universe, I think).<BR>
<BR>
Does Time.T have a large range actually? I haven't figured it out.<BR>
And are negative times allowed?<BR>
If no negative times, then not a wide range.<BR>
<BR>
<BR>> No, but again the fact that C does something is not a good reason for us to do<BR>> it. We need a new language type just to deal with file lengths? I think not.<BR>> That's the only real use case I've seen so far...?<BR>
<BR>
National debt as an integer?<BR>
I don't know if there are other uses.<BR>
<BR>
> Of course it has to be little endian.<BR><BR>
That's what I think, but I might just be corrupted.<BR>
It still needs to abstract/opaque, though, so people don't get confused<BR>
about the lower bits being unsigned, for example.<BR>
<BR>
<BR>
gotta run,<BR>
- Jay<BR>
<BR> </body>
</html>