Fix typos
Change-Id: I5164d92b0b7d9fc4a4ccfc31087887a78a3fb656 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/210056 Reviewed-by: Julien Nabet <serval2412@yahoo.fr> Tested-by: Jenkins
This commit is contained in:
committed by
Julien Nabet
parent
ebbe637cc0
commit
ae0af926f1
@@ -147,7 +147,7 @@ void TabControl::StartDrag( sal_Int8, const Point& )
|
||||
{
|
||||
bInternalMove = true;
|
||||
|
||||
// object is delete by reference mechanism
|
||||
// object is deleted by reference mechanism
|
||||
( new TabControl::TabControlTransferable( *this ) )->StartDrag( this, DND_ACTION_COPYMOVE );
|
||||
}
|
||||
|
||||
|
||||
@@ -200,7 +200,7 @@ static void* pool_take_extent(struct pool* pool, bool allocate)
|
||||
return data;
|
||||
}
|
||||
|
||||
/* Create a memory pool for fix size objects
|
||||
/* Create a memory pool for fixed-size objects
|
||||
* this is a simplified implementation that
|
||||
* is _not_ thread safe.
|
||||
*/
|
||||
@@ -370,7 +370,7 @@ static unsigned int hash_compute( struct hash const * hash, const char* key, int
|
||||
a = b = c = 0xdeadbeef + (length << 2);
|
||||
|
||||
/* we use this to 'hash' full path with mostly a common root
|
||||
* let's now waste too much cycles hashing mostly constant stuff
|
||||
* let's not waste too many cycles hashing mostly constant stuff
|
||||
*/
|
||||
if(length > 36)
|
||||
{
|
||||
|
||||
@@ -76,10 +76,10 @@ processing all
|
||||
and
|
||||
.I #else
|
||||
directives so that it can correctly tell which
|
||||
.I #include,
|
||||
.I #include
|
||||
directives would be used in a compilation.
|
||||
Any
|
||||
.I #include,
|
||||
.I #include
|
||||
directives can reference files having other
|
||||
.I #include
|
||||
directives, and parsing will occur in these files as well.
|
||||
@@ -289,7 +289,7 @@ file exactly once, maintaining an internal symbol table
|
||||
for each.
|
||||
Thus, the first file on the command line will take an amount of time
|
||||
proportional to the amount of time that a normal C preprocessor takes.
|
||||
But on subsequent files, if it encounter's an include file
|
||||
But on subsequent files, if it encounters an include file
|
||||
that it has already parsed, it does not parse it again.
|
||||
.PP
|
||||
For example,
|
||||
|
||||
Reference in New Issue
Block a user