list separator in config entries

[Thomas Braxton]

On 10/17/07, Oswald Buddenhagen <ossi at kde.org> wrote:
>
> On Wed, Oct 17, 2007 at 04:54:09AM -0500, Thomas Braxton wrote:
> > Personally I think this is uglier than hex encoding the trailing
> > backslash.
> >
> - encoding just a trailing backslash is sicko. and it is how the windows
>   shell works wrt quotes, so it can't be good. ;)


i wouldn't know, i stay away from windows as much as possible.

- hex-coding is "a bit" inconsistent with the rest of the escaping.
>   talking surprises ...


not my fault windows uses our escape char as a dir separator, but it's the
only way i could figure out how to let KConfigGroup know that backslash is
special

> Since we can't know if this is a trailing backslash or escaping the
> > separator, every backslash has to be escaped twice. Once by
> > KConfigGroup, and once by KConfigIniBackend
> >
> correct. i said this quite some mails before already.
>
> > And I'm not sure, but I think this will cause problems if/when we
> > change KEntry to use QVariant instead of QByteArray, because there's
> > no way for KConfigIniBackend to know if it should unescape the
> > backslashes once or twice.
> >
> you would have this problem either way as long as the backend does not
> know whether it is dealing with a list in the first place.


KConfigIniBackend will never *know* it is dealing with a list, it can only
guess, unless we start saving the type in the file.

this just shows that the refactoring suggested near the start of this
> thread is a must-have. we won't get anywhere without it, let alone have
> the possibility to add other backends.


I'm sure everyone is ready to wait while we iron out the bugs from changing
KEntry to using QVariant instead of QByteArray. Without another backend this
is alot of something for nothing

--
> Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
> --
> Chaos, panic, and disorder - my work here is done.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071017/5ba82d15/attachment.htm>