On Wed, 2012-02-01 at 09:26 +0100, Stephan Bergmann wrote:
Unless there's someone who screams "but all this should go away in the
next couple months, anyway!" I would therefore go ahead and clean that
code up, ridding it of any tools dependencies (should hopefully not be
too difficult to base it either on sal or even on the plain C++ standard
library).
l10ntools is nearly the only consumer of ByteStrings (including
inheriting from ByteStrings, yippee) left in core, if l10ntools drops
its uses of ByteStrings then ByteString itself can finally go.
So, I'd be a fan of a two-stage pass where ByteString gets removed first
and that pushed so we can remove the rest of ByteString while the rest
of the refactoring is going on :-)
C.
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.