[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KConfig
From:       Michael Kropfberger <michael.kropfberger () gmx ! net>
Date:       1999-02-26 20:50:54
[Download RAW message or body]

Hans Meine wrote:
> 
> On Sun, 21 Feb 1999, Michael Kropfberger wrote:
> >my lately posted problem still exists but I will try to formulate my
> >question in a different way:
> >
> >I am iterating over a list of values out of a QDict and storing it with
> >
> >  KConfigBase::writeEntry(const char *pKey, const char *pValue)
> >
> >and the writeEntry always changes the pValue immediately just by the
> >call itself!!!
> >
> >so I wondered, whats' about the const char *??? I can't get it to work!
> It's probably not what you wanna hear, you may even know, but:
> There is a difference between "const char *" and "char * const". In your case
> only *pValue is a const char, the pointer pValue itself is not const. That
> would be "char * const pValue".

okok... but there is absolutely no position in the code of writeEntry
where
it changes _something_...

I hoped somebody could help!?

bye, 

Mike
-- 
<      ....need an upgrade to Windoze95 or better? install LINUX!      >
<   To iterate is human, to recurse divine.     -- L. Peter Deutsch    >
<---------------------------------------------------------------------->
< /+++/ Michael Kropfberger       (mailto:michael.kropfberger@gmx.net) >
< A-9074 Keutschach 58, Tel.: (04273) 30 41  or (+43664)1233 068 /+++/ >
<---------------------------------------------------------------------->

[prev in list] [next in list] [prev in thread] [next in thread]