Encoding problems due to automatic QByteArray <-> QString casting

[Andreas Pakulat]

On 22.07.09 18:03:14, Milian Wolff wrote:
> Andreas Pakulat wrote:
>> On 22.07.09 16:39:08, Milian Wolff wrote:
>>> Milian Wolff wrote:
>>> . of  course we could use QLatinString but I doubt the huge change would
>>> justify the small gain. What do you think?
>>
>> Is there a way of making them warnings instead of real errors? That would
>> at least allow to enable them now and then try to look at the warnings to
>> check wether we can maybe easily filter out the real problems from the
>> relatively unproblematic c-char array case. Fixing encoding problems
>> without these defines is definetly not a nice job, especially since we're
>> converting back and forth in a couple of places.
>
> Yes, there is a way to set them to warnings. But with all the other  
> cases that would greatly pollute the compile process... I doubt that's  
> easier to find possible errors in the make output...

Hmm, how about making that optional with a single CMake option, i.e. if the
CMake option is set enable both TO_ASCII and FROM_ASCII as warnings. That
way interested developers can see them and eventually find a way to grep
the important ones out.

Andreas

-- 
Your love life will be happy and harmonious.