Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
...otherwise bridges/source/cpp_uno/mingw_intel C++ ABI assumptions would not
meet what i686-w64-mingw32-g++ emits (though it is unclear to me how this shall
ever have worked before, as kendy claims it once did; also, at least for me,
"wine soffice.exe" still does not work, as there is apparently confusion about
C++ exception stack unwinding between GCC and cpp_uno/mingw_intel code).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These are deprecated and not used in LO.
|
|
...which has the necessary features to support it.
Change a lot of classes to either contain a protected non-virtual dtor
(which is backwards compatible, so even works for cppumaker-generated
UNO headers) or a public virtual one.
cppuhelper/propertysetmixin.hxx still needs to disable the warning, as
the relevant class has a non-virtual dtor but friends, which would still
cause GCC to warn.
Includes a patch for libcmis, intended to be upstreamed.
|
|
Except in some unittests, which are sometimes rather silly and
broken about it, which might explain why they're disabled.
|
|
Since OString already has a ctor accepting const char*, I cannot
find out a way to distinguish string literals other than using
a template, otherwise const char* somehow takes precedence
(all of gcc, clang, msvc). But the template requires
the Substitution Is Not A Failure Idiom to actually create
only wanted instances. And the compiler can try evaluate
the OString ctor as a possibility when comparing an int to
an anonymous enum, and anonymous enum as a type without linkage
cannot be a template argument before C++11. SFINAE should still
work, but not with gcc older than 4.0.2 (which we right now
use only on macs). So for that case disable the string literal
ctors, which means macs will have one extra strlen call,
and also that embedded \0's in string literals will be
inconsistent. The tiny performance problem shouldn't matter that
much and will eventually go away, the \0 problem should not
matter, since before string literal ctors were introduced
\0's had not been included anyway unless RTL_CONSTASCII_STRINGPARAM
was used. So we should be safe and when removing the CONSTASCII
macros \0 cases should be handled by explicitly mentioning
the length.
|
|
See:
https://bugs.freedesktop.org/show_bug.cgi?id=44982#c6
https://bugs.freedesktop.org/show_bug.cgi?id=44982#c7
for why.
|
|
|
|
On Linux, public templates should not be hidden at the linker level.
But on Windows, dllimport causes trouble. So create a new macro
to be used specifically with templates that does the right thing
on both platforms.
(http://lists.freedesktop.org/archives/libreoffice/2012-March/028041.html
and followups)
|
|
but that is fine, because outside the unittest it should fail
everywhere
|
|
|
|
To help distinguish between OOo derivatives.
|
|
match() has matchIgnoreAsciiCase(), so it makes sense that endsWith()
also has the IgnoreAsciiCase variant, especially given there already is
endsWithIgnoreAsciiCaseAsciiL()
|
|
|
|
the comment was wrong, char gets converted to const char, not the
other way around
|
|
|
|
|
|
|
|
The AsciiL variants are new for 3.6 anyway, so there's no need to keep
new functions that'd be obsolete before their first release.
|
|
|
|
|
|
this will make it easier to detect errors, rather than making it empty
|
|
This is to prevent things like by mistake doing match( RTL_CONSTASCII_STRINGPARAM("foo")),
which will call match(const char(&)[N], int=0), where the second argument is the fromIndex
argument.
|
|
|
|
Drop the recently introduced rtl_uString_newFromAscii_WithLength()
and replace it with this one. The name fits better and it'll be also
a distinct function that specifically includes embedded \0's
(because that's what OUString supports and if a string literal
explicitly includes it, it makes sense to copy it as such).
|
|
|
|
|
|
otherwise clang warns about things like 1 && 1
|
|
|
|
Otherwise when using a template from another module, an instance
of it may end up being non-exported even though it's used by
something exported.
|
|
...instead of arbitrarily returning certain values when the requested
information is not available.
This reveals a problem in strmunx.cxx that is apparently a regression introduced
with 4a086fca7b0a77c20bc9f1c97507966e2861f3da "fix SvStream to not require a
custom open or lstat method."
|
|
|
|
|
|
|
|
...as the Thread may already have been destroyed by that time.
Also, no need to programmatically check fro programming errors when they
have already been addressed by assert.
|
|
|
|
|
|
|
|
Return value of the function is set by the inline assembler code.
|