Fixes warnings: 'SvXML*_Impl' declared with greater visibility than
the type of its field 'SvXMLExport_Impl::mpRDFaHelper'.

Bug 38831, replace SvULongs with std::vector in sfx2 and related svtools

Replace SvULongs with std::vector<sal_uIntPtr> and SvUShorts with std::vector<sal_uInt16>

Reduce scope of variables declared inside a switch statement. OK, so
make those code snippets into blocks then, to reduce the scope of
those variables. Workaround for weird errors as reported by gcc 4.2.1
in the 10.6 SDK:

SalAquaPicker.cxx: In member function 'void SalAquaPicker::implInitialize()':
SalAquaPicker.cxx:134: error: jump to case label
SalAquaPicker.cxx:127: error:   crosses initialization of 'NSNumber* pExtn'
SalAquaPicker.cxx:126: error:   crosses initialization of 'NSUserDefaults* pDefaults'
SalAquaPicker.cxx:141: error: jump to case label
SalAquaPicker.cxx:127: error:   crosses initialization of 'NSNumber* pExtn'
SalAquaPicker.cxx:126: error:   crosses initialization of 'NSUserDefaults* pDefaults'

Fixes warnings 'SfxStandaloneDocumentInfoObject' declared with greater
visibility than the type of its field
'SfxStandaloneDocumentInfoObject::<anonymous>' and
'SfxStandaloneDocumentInfoObject' declared with greater visibility
than its base 'SfxDocumentInfoO\ bject'.

Last fixes - remove kludge from RepositoryFixes.mk, have redland
build w/o threads for the while, and some hackery to exclude
pointless code like oosplash from android build.

So when using gcc 4.2.1, turn deprecation warnings off for most of
these source files, sigh.

So turn off -Wdeprecated-declarations for most of this source file
when using gcc 4.2.1 or later.

Don't know how to fix it properly (i.e. use the corresponding
non-deprecated API instead), so just using the pragma to ignore that
warning for now...

Unfortunately gcc 4.2.1 doesn't seem to implement the 'GCC diagnostic
push/pop' pragmas, so we just have to ignore the warning for the
method in question and the rest of the file. But luckily it is the
last method;)

We get this warning when compiling with g++ 4.2.1 from the 10.6
SDK. As far as I see there is no command-line option to get rid of it,
and thus also no pragma to avoid it just for the lines of code in
question.

So to make it compile with -Werror also using this compiler/SDK,
expand the Objective-C message call syntactic sugar into a
objc_msgSend() call instead. That should be equivalent, shouldn't it?

To be specific, 'vcl::PageSyncData' declared with greater visibility
than the type of its field 'vcl::PageSyncData::mActions'

Adding a SAL_DLLPRIVATE to the PageSyncData struct, too, then.

Warning was emitted by g++ 4.2.1 against the MacOSX 10.6 SDK.