On Wednesday 25 July 2001 21:41, Aaron J. Seigo wrote:
> i think it comes down to whether or not it offers anything over the current
> approach, and given that KConfig is just group/key/value i don't think it
> does, besides make the code look a little more ugly when a KConfig* is used
> as David pointed out. besides, consistency is nice so there should be one
> and only one way of getting to the config data, and if KDE moved to using
> operator[] then there would be a whole lotta porting going on just to
> change the cosmetics.

Hey, David already convinced me two days ago, and now there are still some 4 
follow-ups (not counting this one) that were sent _after_ that time :-)

This is a closed thread if you ask me...

Martijn