On quinta-feira, 25 de julho de 2013 07:34:19, André Somers wrote:
> Would it be an option to _add_ a qFuzzyCompareMightBeNull or something
> like that then for cases like Juan describes where you don't know if one
> of the two values might be zero or not? There is no reason to change the
> behaviour of the current function (as said in the bug report: it may
> break or slow down other peoples code doing that), but that does not
> hold adding a new function *defined* to do this, right?

So, we should add qFuzzyIsNullOrCompare for people who won't do qFuzzyIsNull
|| qFuzzyCompare?

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

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to