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

List:       kde-core-devel
Subject:    Re: RFC: KConfig changes for 3.0
From:       aleXXX <alexander.neundorf () gmx ! net>
Date:       2001-07-25 18:21:55
[Download RAW message or body]

On Wednesday 25 July 2001 20:11, Charles Samuels wrote:
> On Wednesday 25 July 2001 11:08 am, Martijn Klingens wrote:
> > I fully agree here too, but one question about the syntax: is operator
> > overloading a better way here? Like
> >
> > - config->group("Some Group Name")->readEntry("Some Key");
> > + config[ "Some Group Name" ][ "Some Key" ];
>
> Actually, that would be:
>
> (*(*config)["Some Group Name])["Some Key"];
>
> And frequently, you need the default value for readEntry, which can't be
> done with the operator[]  Unless you want a KConfigEntryMoniker object with
> a operator QString() member.  (Am I going too far?)
>
> I think you can see where the problem with that is :)
>
> If we add dummy classes that wrap around the pointer, it solves that, but
> still... bloaty.  There's also problems with KConfig inheritence (non
> virtual methods for example).
>
> If we could find a clean way to do this, without the bloatyness of the
> wrappers, then I'm ok with it.
>
> -Charles


Only make really sure that it doesn't slow things down, KConfig is a very 
important class regarding app startup speed.

Bye
Alex

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