Re: [boost] Can SVN Check for too long and CamelCase file names?

From: Paul A Bristow (pbristow_at_[hidden])
Date: 2007-08-29 12:19:16

>-----Original Message-----
>From: boost-bounces_at_[hidden] 
>[mailto:boost-bounces_at_[hidden]] On Behalf Of David Abrahams
>Sent: 29 August 2007 17:13
>To: boost_at_[hidden]
>Subject: Re: [boost] Can SVN Check for too long and CamelCase 
>file names?

>on Wed Aug 29 2007, "Paul A Bristow" 
><pbristow-AT-hetp.u-net.com> wrote:
>
>> PS We still need to resolve WHY the original submission 
>rules said "No uppercase". 
>>
>> "These requirements ensure file and directory names are 
>relatively portable"
>>
>>  Are those requirements still valid on some platform?
>
>They are, on case-insensitive filesystems.  If you make a file called
>"Axe.hpp" and then do #include "axe.hpp", it will work on your Windows
>machine under VC++, but will break when someone compiles on linux.

Well one could "say you've got the wrong filename" - on Windows?

But I have no strong feelings on this.  I've just made the mistake of using a capital letter - for fairly good reason - it was
"binomial_NAG_example.cpp"

Are sure there are no files with capitals already?  (Not that I've seen any).

If this is really the policy, it would seem sensible to have it enforced by SVN?

Paul

---
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
[phone] & SMS, Mobile [phone] & SMS
pbristow_at_[hidden]