kconfiggroup and unhandled types

Thomas Braxton kde.braxton at gmail.com
Mon Oct 29 08:46:48 GMT 2007


On 10/29/07, Thiago Macieira <thiago at kde.org> wrote:
>
> Em Monday 29 October 2007 06:24:10 Thomas Braxton escreveu:
> > pretty much. the easiest way would be to write custom versions of
> > readEntry/writeEntry that take care of that for them, then they can just
> > use it like any other type.
> > something like...
>
> I'd much rather there were an external (to the class) overload like
> operator<<
> and operator>>.
>
> Template specialisations are nice, but scary in some compilers...


yeah, but without changing KConfigGroup to using operators instead of
readEntry/writeEntry I don't see another way to do it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071029/4a8f49ed/attachment.htm>


More information about the kde-core-devel mailing list