[ros-dev] RE: [ros-diffs] [sedwards] 19675: XML.cpp -> xml.cpp, XML.h -> xml.h.

[Casper Hornstrup]

> -----Original Message-----
> From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On Behalf Of Steven Edwards
> Sent: 27. november 2005 22:13
> To: ReactOS Development List
> Subject: Re: [ros-dev] RE: [ros-diffs] [sedwards] 19675: XML.cpp -> xml.cpp,XML.h -> xml.h.
> 
> On 11/27/05, Casper Hornstrup <ch at csh-consult.dk> wrote:
> > If the rule is always lowercase filenames why not vote on it and
> > make it official and save ourselves some trouble in the future?
> 
> I don't see why we need a vote for something that is logical and that
> we have maintained everywhere else in the source tree. Its simply a
> defacto standard. I mean you don't want to support MSVC but you want
> to support gcc. Some of us that use gcc use it under Linux because of
> the fact gcc sucks on windows. Be it a make problem, a gcc bug or
> Windows sucking, gcc sucks on Windows and so I and others use Linux to
> cross-compile. Mixed case issues and path seperator issues have always
> been a problem, this is nothing new. With or without a vote if someone
> can still commits a patch with it that will slip through even by
> mistake.
> 
> Thanks
> Steven

It is not logical. See how many .rc files have upper-case first letter
for instance.

I won't actively test my changes on both compilers. I WILL help find
solutions that work on both compilers. There is a big difference.
Supporting MSVC was the reason I made rbuild support multiple backends.
I knew that if it didn't, then we would have had lots of MSVC project
files in the tree today like there currently is for explorer and
rbuild.

When it is documented in wiki, it is more easily remembered. I don't
remember these rules (logical or not) and many others don't either
apparently. Having an explanation of how to do something which can be
easily linked to, makes it easier to agree on what to do the day such
a decision is needed.

Casper