On Wed, Apr 25, 2007 at 01:43:06PM +0200, [EMAIL PROTECTED] wrote:
> On Wed, 25 Apr 2007, Abdelrazak Younes wrote:
>
> >Jean-Marc Lasgouttes wrote:
> >>> > > > > "christian" == christian ridderstrom
> >>> > > > > <[EMAIL PROTECTED]>
> >>> > > > > writes:
> >>
> >>> > > Actually, I propose to merge all these files to FrontendHelpers.
> >>
> >>christian> I probably missed it in the thread, but I thought
> >>christian> UpperCase.cpp was intended for a file that defined the
> >>christian> class UpperCase?
> >>
> >> I would prefer that too.
> >
> >me too.
>
> Bo (and others), did you have an opinion on this?
>
> /Christian
>
> PS. I like to be consistent in the naming, but what are the guidelines?
My rules are more or less:
If there's a single class Foo implemented in the file, it should be
Foo.h/Foo.cpp. That should be the common case.
If there are classes FooSomething, FooHelper, FooSimilar in the file,
it should be named Foo.h/Foo.cpp.
If there are free functions fooHelper, fooSimilar, fooOther in the file,
it should be named Foo.h/Foo.cpp.
Name clashes should be avoided.
There should be no {L,LyX,Q,QL} prefix to class and file names.
Andre'
