[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] kconfig_compiler and C++ file extensions
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-01-13 14:15:07
Message-ID: 200401131515.07694.frans.englich () telia ! com
[Download RAW message or body]

On Tuesday 13 January 2004 14:40, Adriaan de Groot wrote:
> On Tue, 13 Jan 2004, Chris Howells wrote:
> > On Tuesday 13 January 2004 13:24, Frans Englich wrote:
> > > I have no idea what files it's about nor what code, but can't you just
> > > move the files to .cpp equivalents?
> >
> > Why? We don't try to enforce other coding styles (e.g. tabs/versus)
> > spaces on others (unless changing someone's already written code), so
> > extensions should be no different.
>
> Cutting off the thread now, as we're _waaaay_ into bikeshed territory by
> now. I retract my request to commit this now, since I just realized that
> the new KConfigXT stuff that is causing the problem is in
> osnabrueck_branch, so it's no problem to release KDE 3.2 with a no-XT
> version of KPilot.
>
> Post 3.2, I would like to add this feature - or figure out why/how
> autoconf on my system wants .cc extensions for the kcfg files as well.
>
> As for renaming, Frans, we went into this yesterday. 20 percent of KDE
> uses .cc .

Yupp, and my interpretation was that an agreement/unification on extension 
would be appreciated. My idea was to in /this/ case solve the problem by 
renaming the relevant files. In the long run it has the positive effect of 
lessen those 20%.

But you're right - this is a dead end.

Cheers,


			Frans




[prev in list] [next in list] [prev in thread] [next in thread]