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

List:       kde-devel
Subject:    Re: KConfig again
From:       Christoph Neerfeld <Christoph.Neerfeld () home ! ivm ! de>
Date:       1999-05-16 20:59:04
[Download RAW message or body]


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.

-Chris
 
> Then they may or may not write out they keys on exit. Many apps don't even do
> this because kcm modules handle their config keys.... 
> 
> Why cache something that is not used for the vast majority of time for most
> applications?
 
> --
> Daniel M. Duley - Unix developer & sys admin.
> mosfet@kde.org
> mosfet@jorsm.com
> 

--------------------------------------------------------------
Christoph Neerfeld <Christoph.Neerfeld@home.ivm.de>
                   <chris@kde.org>

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