Re: Weird string I/O problem

[anon@anon.org (anon)]

It answers the original poster, That is if one find something they do not like 
in Ada or the RM either work around it or write your own routine. But stop 
complaining about it!

And I did not say MAC. I say OSs that use LF or CR/LF pairing. 

As for you!  You need to learn English. And there are many different ways 
someone can say the same thing.  Just like in programming, there is no 
single way to perform a routine. Some may like the RTL of Ada to do the 
validation, while others prefer the concept of Ravenscar or no RTL.


In <d74c1eb0-676f-43c5-85f4-de82b4c9e581@w35g2000yqm.googlegroups.com>, christoph.grein@eurocopter.com writes:
>On Dec 3, 10:16=A0am, a...@anon.org (anon) wrote:
>> -- For christoph.grein
>> -- =A0 =A0Better re-read RM A.10.7. It does not say what you think it doe=
>s.
>
>??? Hu. I quoted paras (1..3). So what do you think they say?
>
>> -- =A0 =A0Now A.9(8) should be A.10.8. =A0And it says that it is up to th=
>e
>
>Hehe ;-) We're all fond of typos. The correct quote here is A.10(8).
>
>> -- =A0 =A0author's implementation to define the terminators. Normally
>> -- =A0 =A0that is defined by the OS and hardware, but it can be redefined
>> -- =A0 =A0by the author code.
>
>What do you mean with "author"? Who is the author here, the
>implementor (the programmer definitely cannot redefine them)? Of
>course terminators are implementation defined. This is why there are
>End_of_Line and End_of_Page queries. So if you want to write portable
>code, use those, not CR/LF etc. This will simplify the code.
>
>BTW: Doesn't Mac use only CR for End_of_Line? Then anon's code will
>fail again.
>
>anon: I didn't doubt that you are able to write working code. But what
>do you want to demonstrate with this example? It simply does what
>Get_Line does, so what is the advantage of your code? OK, it keeps all
>control characters (except CR and LF and NUL) that might be present in
>the input, but ruins the line and page counts that Text_IO maintains.
>So what?