[patch, libgfortran] PR47694 [4.3/4.4/4.5/4.6 Regression] Fortran read from named pipe fails

Jerry DeLisle jvdelisle@frontier.com
Sat Feb 19 23:26:00 GMT 2011


On 02/19/2011 11:19 AM, Tobias Burnus wrote:
> Jerry DeLisle wrote:
>> Well, I tested. On my system, \r by itself works, \n by itself works, \r\n
>> works, but my system sees it as two lines and not one. That may be normal. I
>> will have to get it tested on a cr-lf based system.
>
> I have not tested it, but at least for normal files - and possibly also for
> sockets*, I would like under Unix to have "\r\n" and "\n" be read as single EOR
> marker. I do not want to have "\r\n" as two new lines. (Similarly, I also would
> like to read Unix "\n" files correctly on Winows.) I think the current code
> (without patch) and the submitted patch handle this correctly, though I have not
> extensively tested it.
>
> (I do not care about "\r" as end of line marker as it effectively plays no role
> [1].)
>
> Tobias
>
> * e.g. internet protocols often require to use \r\n [1]
>
> [1] http://en.wikipedia.org/wiki/Newline#Representations
>

Doesn't Mac use just \r by itself?

Jerry



More information about the Fortran mailing list