Re: Draft Standard Text, V02.1
Friends,
Thanks, John.
Reading this made me think of an issue perhaps worth some discussion: I/O.
I might consider offering a motion: Since P1788 is a hardware standard, questions of input and output are not within the scope of the standard.
Comments?
Interval I/O is a fruitful topic for discussion. However, it seem to me that interval I/O is entirely a language issue, not a hardware issue.
In John's draft standard (section 5.4.1), he specifies an interval constructor floats2interval(). That makes sense. He also lists a constructor text2interval(). If we are specifying an interval language/environment, I agree. If we are specifying interval hardware, I think it is out of scope.
Similarly, I note almost no mention of interval output in these discussions. I think that is exactly right.
Frequently, I have argued here for SIMPLICITY. Let's leave interval I/O out of this hardware standard.
George
On Mar 14, 2010, at 10:25 AM, John Pryce wrote:
> P1788
>
> At last I have revised the draft Standard Text in the light of comments received. I urge EVERYONE to read this Version 02, sub-version 1, and give me comments, even if these are only that you (a) like it or (b) hate it.
>
> I think we are at a stage where parts, at least, of this document can be voted on to become official text. I shall discuss with the Officers in the next days on the best procedure to put this in hand.
>
> The Latex of this version is Revision 22 on the P1788 subversion server.
>
> Best wishes
>
> John Pryce
> <P1788_MAIN.pdf>
Dr. George F. Corliss
Electrical and Computer Engineering
Marquette University
P.O. Box 1881
1515 W. Wisconsin Ave
Milwaukee WI 53201-1881 USA
414-288-6599; GasDay: 288-4400; Fax 288-5579
George.Corliss@xxxxxxxxxxxxx
www.eng.mu.edu/corlissg