2011/7/26 Marc-André Laverdière <marc-andre@atc.tcs.com>:
This patch is bringing up a small question:
I thought we were trying to standardize the code to use sal_* types
everywhere...
Can anyone confirm/deny that?
No, not exactly.
it is actually the intention to use bool/true/false unless that break
the UNO API (and for 4.0 we will make sure that UNO API do suport the
native bool type, so that sal_Bool will be indeed strictly equal to
bool)
the goal is also to get rid of BOOL, but again being careful with uno
interaction: if uno -> sal_Bool otherwise bool
(this is particularly tricky when touching the prototype of a virtual
function... as all of the derived virtual of a given function must be
change at once)
Norbert
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.