RFC: KConfig & Lock File API

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue April 27 2004 20:13, Frerich Raabe wrote:
> On Tuesday 27 April 2004 17:31, Waldo Bastian wrote:
> > I would like to have your comments on the following API changes.
>
> A ctor overload which automatically calls lock() would be very nice (that
> is, another ctor which takes an int parameter), so that one can create
> locks in one line and use curly braces to define the scope of the lock
> (much like KConfigGroupSaver).

Something like
	KConfig( const QString& fileName = QString::null, int lockOptions); ?

I agree that the ability to lock before actually reading anything would be 
nice, I'm not sure I like yet another constructor. I wonder if it would be 
possible to delay the actual reading of the config file till something 
actually access the config data. That way it would be possible to lock the 
file after construction but before it has read anything.

Cheers,
Waldo
- -- 
bastian at kde.org  |   SUSE Linux 9.1 Order Now!   |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAkXU6N4pvrENfboIRAnyUAJ9Bu1nA8T1RV+moUhSDrlFYoMHqcwCgqXdo
+vd3+xBpURnBcNqZpYmVyDk=
=MDUd
-----END PGP SIGNATURE-----