Note that instead of a SAL_WARN as you have, I output the undefined value
as a number. That is more useful.
... because if somebody would happen to notice a warning "Unknown
RectanglePoint Value", what would their first reaction be?
Exactly, "Infuriating, why can't it then show *what* the unknown value is,
that would help me figuring out what is going on?"
Warning messages, intended for developers to see, about values being
unexpected or undefined, should always show what the encountered unexpected
or undefined value is.
(Again, just my opinion, of course.)
--tml
Context
- Re: 'StylePoolImpl::createIterator': function does not take 0 arguments (continued)
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.