Camelcase for sourcecode filenames?

[Jeff Mitchell]

NTFS and HFS+ are both case-preserving but not case sensitive.  
(Technically HFS+ can be case sensitive but because of idiot programmers 
in many major applications, this always breaks your OS X system).

I'm not sure how they handle file renames, i.e. foo -> Foo but I imagine 
just fine.  There's more of a problem on FAT32 (case preserving but with 
limitations, especially when trying to switch cases), but people using 
that should get with the program...

--Jeff

Seb Ruiz wrote:
> I use camel case for java development on windows and linux, works no problems.
>
> On 11/05/07, Mark Kretschmann <markey at web.de> wrote:
>   
>> Hi,
>>
>> a while ago Nikolaj and I were talking about using camelcase in our filenames,
>> e.g., instead of "singlecollectiontreeitemmodel.h"
>> using "SingleCollectionTreeItemModel.h", as this can be more readable. Back
>> then I wasn't sure if this is properly supported on all our platforms
>> (Windows, MacOS).
>>
>> Does anyone know if it's safe to use this on all platforms? And what's your
>> opinion on it?
>>
>> --
>> Mark
>> _______________________________________________
>> Amarok-devel mailing list
>> Amarok-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/amarok-devel
>>
>>     
>
>
>