diff options
Diffstat (limited to 'framework/source/fwi')
| -rw-r--r-- | framework/source/fwi/classes/protocolhandlercache.cxx | 4 | ||||
| -rw-r--r-- | framework/source/fwi/threadhelp/lockhelper.cxx | 16 | ||||
| -rw-r--r-- | framework/source/fwi/threadhelp/transactionmanager.cxx | 2 |
3 files changed, 11 insertions, 11 deletions
diff --git a/framework/source/fwi/classes/protocolhandlercache.cxx b/framework/source/fwi/classes/protocolhandlercache.cxx index f1e782dd8560..e558cd64a670 100644 --- a/framework/source/fwi/classes/protocolhandlercache.cxx +++ b/framework/source/fwi/classes/protocolhandlercache.cxx @@ -65,7 +65,7 @@ PatternHash::iterator PatternHash::findPatternKey( const OUString& sURL ) /** @short initialize static member of class HandlerCache @descr We use a singleton pattern to implement this handler cache. - That means it use two static member list to hold all neccessary information + That means it use two static member list to hold all necessary information and a ref count mechanism to create/destroy it on demand. */ HandlerHash* HandlerCache::m_pHandler = NULL; @@ -148,7 +148,7 @@ sal_Bool HandlerCache::search( const OUString& sURL, ProtocolHandler* pReturn ) /** @short search for a registered handler by using an URL struct - @descr We combine neccessary parts of this struct to a valid URL string + @descr We combine necessary parts of this struct to a valid URL string and call our other search method ... It's a helper for outside code. */ diff --git a/framework/source/fwi/threadhelp/lockhelper.cxx b/framework/source/fwi/threadhelp/lockhelper.cxx index 0a05c66b0011..8a7edefc8233 100644 --- a/framework/source/fwi/threadhelp/lockhelper.cxx +++ b/framework/source/fwi/threadhelp/lockhelper.cxx @@ -93,7 +93,7 @@ LockHelper::~LockHelper() we must simulate it as a write access! @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method acquireWriteAccess() @@ -115,7 +115,7 @@ void LockHelper::acquire() we must simulate it as a write access! @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method releaseWriteAccess() @@ -136,7 +136,7 @@ void LockHelper::release() Writing isn't allowed then - but nobody could check it for you! @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method releaseReadAccess() @@ -156,7 +156,7 @@ void LockHelper::acquireReadAccess() @descr A guard should call this method to release read access on your member. @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method acquireReadAccess() @@ -178,7 +178,7 @@ void LockHelper::releaseReadAccess() After successfully calling of this method you are the only writer. @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method releaseWriteAccess() @@ -198,7 +198,7 @@ void LockHelper::acquireWriteAccess() @descr A guard should call this method to release write access on your member. @attention If a shareable osl mutex exist, he must be used as twice! - It's neccessary for some cppu-helper classes ... + It's necessary for some cppu-helper classes ... @seealso method acquireWriteAccess() @@ -223,10 +223,10 @@ void LockHelper::releaseWriteAccess() @attention a) Don't call this method if you are not a writer! Results are not defined then ... - An upgrade can't be implemented realy ... because acquiring new access + An upgrade can't be implemented really ... because acquiring new access will be the same - there no differences! b) Without function ... - because, a mutex don't support it realy. + because, a mutex don't support it really. @seealso - diff --git a/framework/source/fwi/threadhelp/transactionmanager.cxx b/framework/source/fwi/threadhelp/transactionmanager.cxx index d34e79fc492c..1772515531bd 100644 --- a/framework/source/fwi/threadhelp/transactionmanager.cxx +++ b/framework/source/fwi/threadhelp/transactionmanager.cxx @@ -65,7 +65,7 @@ TransactionManager::~TransactionManager() @short set new working mode @descr These implementation knows for states of working: E_INIT, E_WORK, E_CLOSING, E_CLOSE You can step during this ones only from the left to the right side and start at left side again! - (This is neccessary e.g. for refcounted objects!) + (This is necessary e.g. for refcounted objects!) This call will block till all current existing transactions was finished. Following results can occur: E_INIT : All requests on this implementation are refused. |