QString vs. QCString

[John Birch]

IIRC I think it was because in QT1.4 - yes that is 1.4 and not a typo, 
(prehistoric I know):-) - QString was 8bit byte based and I used that for gdb 
data. (Hmmm was there also QCString at that point? I forget now)

In converting to QT2 I converted some to QString but some didn't go easily so 
I just used QCString to get it finished.

I'd convert them to QString if I was you :-)

jbb

On Wednesday 15 March 2006 03:34, Jens Dagerbo wrote:
> I guess your best chance for a non-guess answer would be to mail John
> Birch directly. I really doubt anyone but him could answer with any
> weight.
>
> I have a vague memory of discussing the QCStrings with him a few years
> back. Basically (and again, IIRC) his attitude was "if it ain't
> broken, don't fix it". This against the background that he at that
> point was already becoming less active in the project.
>
> Personally, I think having just one string class to deal with is a
> very good idea. :)
>
> // jens
>
> On 3/14/06, Vladimir Prus <ghost at cs.msu.su> wrote:
> > Hi!
> > At the moment, debugger code uses both QString and QCString, and that's
> > pretty incovenient, especially given that interfaces for those classes a
> > bit different.
> >
> > I don't really see any need for QCString. Yes, replies from gdb are 8-bit
> > strings, but who cares if we use double the memory?
> >
> > So, I plan to eventually kill all uses of QCString and use QString. But I
> > though maybe somebody knows good reasons why I should not do this?
> >
> > - Volodya
> >
> > _______________________________________________
> > KDevelop-devel mailing list
> > KDevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel