Hello!
> > This allows the same source to be compiled from the same location for
> > multiple platforms.
>
> Only because either your Windows or Unix compilers are willing to
> compile defective text files. (I'm guessing that it's the Windows
> compiler since it's fairly natural to ignore missing <CR>s, it's not
> nearly as natural to ignore extra ones. In fact, I wouldn't be
> surprised if the Solaris compilers refused to compile DOS-format files.)
Sorry for interfering, but the original message said
>>> the UNIX version barfs because the DOS version leaves ^M cookies at
>>> the end of each line in CVS/Entries, CVS/Repository, CVS/Root
This is not about source files and compilers.
I think that developers should not be encouraged to use "cvs commit" as
way of transmitting files from one system to another. Many sites require
that files are committed after testing on more than one platform.
My former employer required testing on 2 platforms for check-ins on the
development branch and 6 (!!!) platforms for check-ins on the stable
branch. This could be acomplished with "views" in ClearCase, but CVS would
be of little help here.
Let's leave it up to the build system to deal with shared working
directories. Autoconf-enabled projects, for instance, can be built for
many platforms from the same source directory. The question whether the
working directory should be shared is out of scope of CVS.
I see nothing bad if CVS did its best to recognize all types of line
endings.
I'm omitting cc: to bugs-cvs. We have yet to persuade others that it's a
bug in CVS.
Regards,
Pavel Roskin
