Re: [boost] Line endings in source files

From: William E. Kempf (williamkempf_at_[hidden])
Date: 2002-08-08 17:15:07

----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>

> At 04:49 PM 8/8/2002, Paul Mensonides wrote:
>
>  >> Following up on an earlier discussion, I wrote a little script to
check
>  >> line endings in Boost files.  See below for the files found to have at
>  >> least one '\r' line ending.
>  >>
>  >> In checking a few of these to make sure the script was correct, I
> noticed
>  >> line endings in the form "\r\r\n". In hex, 0D 0D 0A.
>  >>
>  >> What's happening here? This isn't a form I'm familiar with.
>  >
>  >This happens when you upload a file that has Windows line endings from a
>  >Unix CVS.  I.e. it doesn't modify the line endings because it assumes
>  >they are already correct.
>
> I don't understand; it would help if you could rephrase using CVS
> terminology - my WinCVS client has "commit" or "update" commands, but no
> "upload" that I'm aware of.
>
> By "upload a file that has Windows line endings from a Unix CVS", do you
> mean "commit a file that has Windows line endings to a CVS running on a
> UNIX system"?
>
> Or maybe "update a file that has Windows line endings from a CVS running
on
> a UNIX system"?

If I understand him, then both.

> Both of those operations happen all the time, yet don't modify line
> endings.

The problem occurs when a file on Unix has DOS line endings.  This should
rarely occur, since checking a file out of CVS will usually convert line
endings to the native Unix type.  But say you work in both environments and
you transfer a file from your Windows box to the Unix box with some
mechanism that doesn't conver the line endings, such as a binary FTP (just
one of many examples possible here).  You then commit or update CVS with
this file and you get \r\r\n.

At least I think that's what he's describing.

Bill Kempf