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

List:       kde-devel
Subject:    Re: KConfig again
From:       Harri Porten <porten () tu-harburg ! de>
Date:       1999-05-16 21:46:01
[Download RAW message or body]

Mosfet wrote:
> 
> On Sun, 16 May 1999, Christoph Neerfeld wrote:
> > On 17-May-99 Mosfet wrote:
> > >
> > > And also how KConfig is used. As I mentioned before, almost all apps read in
> > > the KConfig items they want in their constructors and put them in local data
> > > structures. They do not call readEntry a bunch of times throughout the
> > > program.
> >
> > I don't know what other developers do, but I tend to keep the information in
> > config objects and don't copy it to local variables. But of course I would do it
> > if I knew that KConfig rereads the file every time.
> 
> This does not seem to be a good idea in any case. If you need to access a key
> many times it seems better to load it into a variable than calling KConfig over
> and over.

Why ? If speed hasn't the highest priority why should I add that
overhead (with the current KConfig) ?
kppp for example has at least ~70 entries in its rc file that always
have to be accessible. Why should I store them again ?

Harri.

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