Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> We have a religiuos problem here as we are/were not supposed to use >> QString in support. > > That's not true anymore as we do us it now.
Not in the api, do we? I do not see the point to introduce it in the API just to shave a toqstr() call. I do not think this has any measurable cost in terms of size/speed of the _final_ binary. JMarc
