list separator in config entries

[Thomas Braxton]

>
> FYI, PutHuhn is working on it. Andreas Pakulat, Ossi and me all have
> been talking to him as he is closest to being a maintainer of KConfig.
> And yes, of course the tests have been put there to fail. They
> specifically test for the problem that we have now. And no, having
> some input break KConfig is not an option, however silly that string
> might look to you. This also has security implications, and it's
> terrible style to break on some input due to implementation problems.

again why are you storing strings with backslashes if they aren't Windows
paths? And if they are you should be using the Path functions not the
QString functions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071008/ce3599e9/attachment.htm>