NICE Eiffel Standards Group -- Library Committee Mailing List To post to list: NICE-ESG-Libs@atlanta.twr.com To send mail to the Chairman of the committee: NICE-ESG-Libs-chair@atlanta.twr.com Administrative matters (sign up, unsubscribe, mail problems, etc): NICE-ESG-Libs-request@atlanta.twr.com
Date: Thu, 1 Jun 95 19:15:30 PDT From: bertrand@vienna.eiffel.com (Bertrand Meyer) Subject: Revised document To: nice.lib@vienna.eiffel.com, Steve_Tynor@vienna.eiffel.com Copy to: From: Bertrand Meyer Mailer: BOOM I have revised the document (v. 8) and put it in the usual place. All the apparatus is there, i.e. a new README, the diff files (*-DIFF-7-8, *-DIFF-7-8.ps) etc. All the discussed modifications have been carried out with the following exceptions: - I forgot to add the mention of provisional nature of FILE and STD_FILES. This will be fixed. - Instead of `read_next_line' I used `to_next_line' as the new name for `next_line'. It struck me that `read_next_line' was confusing, as it suggested that a line is read, whereas all that happens is that input goes to the next line. What caught my attention is that there already is `read_line', which does what the name suggests. `to_next_line' is not ideal either as it does not suggest input. `input_to_next_line' is my current favorite. Any better suggestion? - I did not remove the preconditions `readable' for file. I don't see how we can do without a precondition for input routines stating that the file is readable. My inclination would be to add `readable' as a query. Suggestions welcome. Best regards, -- BM
Date: Thu, 1 Jun 95 22:45:27 EDT From: tynor (Steve Tynor) Subject: Revised document To: bertrand@eiffel.com, nice-esg-libs Bertrand wrote: | `input_to_next_line' is my current favorite. Any better suggestion? Our current libraries use `skip_to_next_line'. Steve
