$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Chris Little (cslittle_at_[hidden])
Date: 2002-07-05 20:32:24
on 7/5/02 8:40 PM, Michael Stevens at support-1_at_[hidden] wrote:
>
>
>> From: "Paul A. Bristow" <boost_at_[hidden]>
>>
>> The reason is that many files contain CR, CR (0x0D, 0x0D)
>> rather than CR, LF ( 0x0D, 0x0A) in quite a few places.
>> These are invisible to the MS IDE editor and Textpad,
>> except in binary display mode. Linux/Microsoft difference?
>>
>> After much scratching of my head,
>> and eventually removal of tuffs of hair,
>> I conclude this produces terminal confusion to the compiler,
>> and to me!
>>
>>
> This is most odd. I can certainly confirm that although the VC7 editor
> has no problem with CR only line termination the compile seems sometimes
> to treat them as an EOF.
> The odd thing is I have never seen CR only (the CR CR is infact 2 lines)
> line termination before,. LF only is the usual UNIX format, CRLF the old
> DOS format. The compilers work fine with either of these but sequences
> of CR only are bad news.
>
> The other odd thing is that I have no problems with the uBLAS files I
> pulled from boost CVS. Infact they seem to be CRLF terminated. Maybe
> this is due to some kind of CVS configuration problem.
>
> Michael
CR only as a line ending is used on Mac's. I don't know that this has
anything to do with the problem that Paul is seeing except that text files
with CR only line endings do exist.
Chris