Comments on: Sensitivity: A Case for Convention. http://virtualinfinity.net/wordpress/program-design/2008/01/28/a-case-for-convention/ Daniel Pitts' Tech Blog Sat, 22 Nov 2008 02:48:21 +0000 http://wordpress.org/?v=2.6.3 By: Daniel http://virtualinfinity.net/wordpress/program-design/2008/01/28/a-case-for-convention/#comment-138 Daniel Tue, 29 Jan 2008 16:23:18 +0000 http://virtualinfinity.net/wordpress/program-design/2008/01/28/a-case-for-convention/#comment-138 I was actually going to mention the double-danger of this in CVS/SVN on windows. I have had issues changing the case of a file/directory changing (I develop on Linux) causing problems for others (who often use windows). BTW. SVN uses bdb to store your files, so the names are OS independent (i.e. SVN server on Windows can still handle FOO and Foo). The solution I found for this was to have the Windows users check out the whole module from scratch again. I was actually going to mention the double-danger of this in CVS/SVN on windows. I have had issues changing the case of a file/directory changing (I develop on Linux) causing problems for others (who often use windows).

BTW. SVN uses bdb to store your files, so the names are OS independent (i.e. SVN server on Windows can still handle FOO and Foo).

The solution I found for this was to have the Windows users check out the whole module from scratch again.

]]> By: Aviad Ben Dov http://virtualinfinity.net/wordpress/program-design/2008/01/28/a-case-for-convention/#comment-134 Aviad Ben Dov Tue, 29 Jan 2008 04:48:30 +0000 http://virtualinfinity.net/wordpress/program-design/2008/01/28/a-case-for-convention/#comment-134 Wow. This happened to me but in a worst-case-scenario. I was reviewing some old code, when I noticed a class which was called "concreteClass" (that is, the class' name started with a non-capital letter). I refactored it for renaming (to "ConcreteClass"), it was successful, I checked it into SVN, and viola! Done. Later on, when other people checked out that file, their local SVN client got stumbled on it - apparently, it didn't DELETE the old file when I renamed it, so it tried to check out Both types of files ("concreteClass" AND "ConcreteClass") and since they were using Windows computers it just didn't work. Obviously it didn't give a reasonable error to find why it was getting stuck but luckily we managed to deduce it was due to these two filenames with conflicting names under Windows (Our SVN repository is kept on a Unix machine so it had no problem keeping the files like that itself.) Phew. Longer response than I thought it would be. :) Wow. This happened to me but in a worst-case-scenario. I was reviewing some old code, when I noticed a class which was called “concreteClass” (that is, the class’ name started with a non-capital letter). I refactored it for renaming (to “ConcreteClass”), it was successful, I checked it into SVN, and viola! Done.

Later on, when other people checked out that file, their local SVN client got stumbled on it - apparently, it didn’t DELETE the old file when I renamed it, so it tried to check out Both types of files (”concreteClass” AND “ConcreteClass”) and since they were using Windows computers it just didn’t work. Obviously it didn’t give a reasonable error to find why it was getting stuck but luckily we managed to deduce it was due to these two filenames with conflicting names under Windows (Our SVN repository is kept on a Unix machine so it had no problem keeping the files like that itself.)

Phew. Longer response than I thought it would be. :)

]]>