[Development] QString behavior change

[Thiago Macieira]

On Friday 31 July 2015 09:48:08 Oswald Buddenhagen wrote:
> well, that recommendation is reasonable in face of the status quo, but 
> i think we should (and could) do a better job at preserving nullness.
> there are only a handful of cases where the choice is arbitrary, and we
> can clearly document them.

In this particular case, it was reasoned that the API was inconsistent and 
broken. So the behaviour was changed intentionally.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center