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

List:       kde-devel
Subject:    Re: KConfig
From:       Hans Meine <hansmeine () dial-net ! de>
Date:       1999-02-25 20:14:38
[Download RAW message or body]

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".
I hope such stupid answers are not called spamming... ;-)

--

Ciao,
   /  /
  /--/
 /  / ANS

---------------------------------------------------------------------
Hans Meine                                mail me: hans_meine@gmx.net
Harkortstr. 138                       http://www.dialnet.de/hansmeine
D-22765 Hamburg                              ICQ: RastaJoe <28674493>
[Germany]                                     Phone: ++49-40-38612523
---------------------------------------------------------------------

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