7be255156f
Just like qMalloc/qRealloc/qFree, there is absolutely no reason to wrap these functions just to avoid an include, except to pay for it with worse runtime performance. On OS X, on byte sizes from 50 up to 1000, calling memset directly is 28-15% faster(!) than adding an additional call to qMemSet. The advantage on sizes above that is unmeasurable. For qMemCopy, the benefits are a little more modest: 16-7%. Change-Id: I98aa92bb765aea0448e3f20af42a039b369af0b3 Reviewed-by: Giuseppe D'Angelo <dangelog@gmail.com> Reviewed-by: John Brooks <john.brooks@dereferenced.net> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Lars Knoll <lars.knoll@nokia.com> |
||
---|---|---|
.. | ||
qabstractprintdialog | ||
qcolordialog | ||
qdialog | ||
qerrormessage | ||
qfiledialog | ||
qfiledialog2 | ||
qfilesystemmodel | ||
qfontdialog | ||
qinputdialog | ||
qmessagebox | ||
qprogressdialog | ||
qsidebar | ||
qwizard | ||
dialogs.pro |