Re: GConf design goals.



Colm Smyth wrote:

> Making a choice about how to store configuration is important for the
> longevity of that data and the ease with which it may be shared with
> other data; that is the crux of why I have been arguing (repeatedly)
> against structures in the configuration data.  They are a convenience
> feature that is likely to break forward compatibility of configuration
> data and make the data implicit rather than explicit at the level of the
> GConf API.

I consider the possibility to store CORBA_any as more flexible, since I
do not make any restrictions to the data which can be stored.

Your argument is to protect users from doing strange things. I simply think
you can't protect someone from making errors. Maybe you can make I a
bit more unlikely. On the other side there are many usage scenarios where
structures are perfectly well, and I want to allow the use of structures
where
it is useful.

- Dietmar





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]