Re: File encoding for files ported between Mac and Windows?
Re: File encoding for files ported between Mac and Windows?
- Subject: Re: File encoding for files ported between Mac and Windows?
- From: Alastair Houghton <email@hidden>
- Date: Tue, 5 Jan 2010 19:12:22 +0000
On 5 Jan 2010, at 18:54, Dix Lorenz wrote:
> How are you porting the files? You should be using some kind of Version Control System anyway and that way, when you check the sources out, they will be correctly formatted for the platform you are on.
That's actually a *massive* mis-feature of many version control systems. Why? Because many people have network-based home directories (particularly in larger companies) and this kind of abject stupidity from SCM systems commonly results in huge change sets full of line ending changes simply because someone checked code out on one platform (to their home folder, which is mounted in more than one place) and then checked in on another.
You may say "don't do that", but it isn't so obvious actually. For instance, it's easy enough to set up a project that will build on OS X using Xcode, on Windows using Visual Studio, and on various UNIXen using a Makefile, all from the same source folder. It seems eminently reasonable then that you should be able to check it out once, and build and edit from all of those platforms, particularly if you have a network-based home folder.
Programmers' editors and compilers generally don't care whether there are CRs or not. Some of them might not like traditional Mac or Amiga text files (which just had CRs and no LFs), but those are rarely necessary anyway.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden