Fix typos
Change-Id: I6fe3f626864db63b1c5ce8af9598730057a9d0eb Reviewed-on: https://gerrit.libreoffice.org/c/core/+/209943 Tested-by: Julien Nabet <serval2412@yahoo.fr> Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
This commit is contained in:
committed by
Julien Nabet
parent
3852fcbb21
commit
bfc5912fbb
@@ -32,7 +32,7 @@ namespace cppu {
|
||||
/** Converts the value stored in an any to a concrete C++ type.
|
||||
The function does the same as the operator >>= () at the
|
||||
Any class, except that it throws an IllegalArgumentException in case of
|
||||
failures (the value cannot be extracted without data loss )
|
||||
failures (the value cannot be extracted without data loss)
|
||||
|
||||
@exception css::lang::IllegalArgumentException when the type could not be converted.
|
||||
*/
|
||||
|
||||
@@ -18,10 +18,10 @@ extern "C" {
|
||||
|
||||
/* On iOS and perhaps Android static linking of the LO code into one
|
||||
* executable (on Android, into one shared library) is used. In order to get
|
||||
* the needed UNO component linked in, the "main" code for an app needs to
|
||||
* implement the lo_get_libmap() function to map UNO component library names
|
||||
* as produced in a build for iOS (like configmgr.uno.a or libsclo.a) to the
|
||||
* corresponding component_getFactory functions.
|
||||
* the needed UNO components linked in, the "main" code for an app needs to
|
||||
* implement the lo_get_factory_map() and lo_get_constructor_map() functions
|
||||
* to map UNO component library names as produced in a build for iOS (like
|
||||
* configmgr.uno.a or libsclo.a) to the corresponding component_getFactory functions.
|
||||
*/
|
||||
|
||||
typedef struct {
|
||||
|
||||
@@ -39,7 +39,7 @@ extern "C" {
|
||||
empty. This is a macro instead of a (C++ inline) function to allow for
|
||||
maximum performance in both C and C++.
|
||||
|
||||
If possible, use the rtl_Instance template instead of explicitly spelling
|
||||
If possible, use the rtl::Instance template instead of explicitly spelling
|
||||
out the double-checked locking pattern. There are few cases where you
|
||||
will have to spell it out explicitly (e.g., the logic of a certain
|
||||
instance of the pattern is too complex to be mapped to the template, or
|
||||
|
||||
Reference in New Issue
Block a user