このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。

翻訳前ページへ


全世界の 機能(する)/行事s in Namespace in Sourcefile 荷を降ろす.h
Language

The 解放する/自由な and Open 生産性 控訴
解放(する)d: Apache OpenOffice 4.1.15

API

SDK

Tips ‘n’ Tricks

Miscellaneous


全世界の 機能(する)/行事s in 全世界の Namespace C++
in Sourcefile 荷を降ろす.h


rtl_addUnloadingListener
extern "C"
sal_Int32 rtl_addUnloadingListener(
rtl_unloadingListenerFunc callback,
無効の * _this );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

Description
The 機能(する)/行事 登録(する)d an 荷を降ろすing listener. The callback argument is a 機能(する)/行事 which is called when the 荷を降ろすing 手続き has been 始めるd by a call to rtl_unloadUnusedLibraries. The second argument is used to distinguish between different listener instances and may be NULL. It will be passed as argument when the callback 機能(する)/行事 is 存在 called. The return value identifies the 登録(する)d listener and will be used for 除去するing the listener later on. If the same listener is 追加するd more then once then every 登録 is 扱う/治療するd as if made for a different listener. That is, a different cookie is returned and the callback 機能(する)/行事 will be called as many times as it has been 登録(する)d.
Parameters
callback
- a 機能(する)/行事 that is called to 通知する listeners.
this
- a value to distinguish different listener instances
Return
identifier which is used in rtl_removeUnloadingListener

rtl_moduleCount_acquire
extern "C"
無効の rtl_moduleCount_acquire(
rtl_ModuleCount * that );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

要約
Default 実施 for rtl_ModuleCount.acquire. Use this 機能(する)/行事 along with rtl_StandardModuleCount.

rtl_moduleCount_canUnload
extern "C"
sal_Bool rtl_moduleCount_canUnload(
rtl_StandardModuleCount * that,
TimeValue * libUnused );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

要約
Default 実施 for component_canUnload. Use this 機能(する)/行事 along with rtl_StandardModuleCount.

rtl_moduleCount_release
extern "C"
無効の rtl_moduleCount_release(
rtl_ModuleCount * that );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

Description
Default 実施 for rtl_ModuleCount.解放(する). Use this 機能(する)/行事 along with rtl_StandardModuleCount.

rtl_registerModuleForUnloading
extern "C"
sal_Bool rtl_registerModuleForUnloading(
oslModule module );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

要約
By 登録(する)ing a module, one 宣言するs that a module supports the 荷を降ろすing 機械装置. One 登録(する)s a module by calling this 機能(する)/行事.

Description
A module can only be 荷を降ろすd from memory when it has been 登録(する)d as many times as it has been 負担d. The 推論する/理由 is that a library can be "負担d" several times by osl_loadModule within the same 過程. The 機能(する)/行事 will then return the same module 扱う because the library will 効果的に only be 負担d once. To 除去する the library from memory it is necessary to call osl_unloadModule as often as osl_loadModule was called. The 機能(する)/行事 rtl_unloadUnusedModules calls osl_unloadModule for a module as many times as it was 登録(する)d. If, for example, a module has been 登録(する)d one time いっそう少なく then osl_loadModule has been called and the module can be 荷を降ろすd then it needs a call to rtl_unloadUnusedModules and an explicit call to osl_unloadModule to 除去する the module from memory.

A module must be 登録(する)d every time it has been 負担d さもなければ the 荷を降ろすing 機械装置 is not 効果的な.

Before a module is 登録(する)d, one has to make sure that the module is in a 明言する/公表する that 妨げるs it from 存在 荷を降ろすd. In other words, component_canUnload must return sal_False. Assuming that component_canUnload returns sal_True and it is 登録(する)d regardless, then a call to rtl_unloadUnusedModules 原因(となる)s the module to be 荷を降ろすd. This 荷を降ろすing can be 始める,決める off by a different thread and the thread which 登録(する)d the module is "unaware" of this. Then when the first thread tries to 得る a factory or calls another 機能(する)/行事 in the module, the 使用/適用 will 衝突,墜落, because the module has been 荷を降ろすd before. Therefore one has to 確実にする that the module cannot be 荷を降ろすd before it is 登録(する)d. This is 簡単に done by 得るing a factory from the module. As long as a factory or some other 反対する, which has been created by the factory, is alive, the component_canUnload 機能(する)/行事 will return sal_False.

負担ing and 登録(する)ing have to be in this order:

  • 負担 a library (osl_loadModule)
  • get the component_getFactory 機能(する)/行事 and get a factory
  • 登録(する) the module (rtl_registerModuleForUnloading
Usually the service 経営者/支配人 is used to 得る an instance of a service. The service 経営者/支配人 登録(する)s all modules which support the 荷を降ろすing 機械装置. When the service 経営者/支配人 is used to get service instances than one does not have to bother about 登録(する)ing.
Parameters
module
a module 扱う as is 得るd by osl_loadModule 
Return
sal_True - the module could be 登録(する)d for 荷を降ろすing, sal_False さもなければ

rtl_removeUnloadingListener
extern "C"
無効の rtl_removeUnloadingListener(
sal_Int32 cookie );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

Description
Listeners (the callback 機能(する)/行事s) must be unregistered before the listener code becomes 無効の. That is, if a module 含む/封じ込めるs listener code, すなわち callback 機能(する)/行事s of type rtl_unloadingListenerFunc, then those 機能(する)/行事s must not be 登録(する)d when component_canUnload returns sal_True.
Parameters
cookie
is an identifier as returned by rtl_addUnloadingListener 機能(する)/行事.

rtl_unloadUnusedModules
extern "C"
無効の rtl_unloadUnusedModules(
TimeValue * libUnused );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

Description
This 機能(する)/行事 始める,決めるs off the 荷を降ろすing 機械装置. At first it 通知するs the 荷を降ろすing listeners ーするために give them a chance to do cleanup and get their threads in a 安全な 明言する/公表する. Then all 登録(する)d modules are asked if they can be 荷を降ろすd. That is, the 機能(する)/行事 calls component_canUnload on every 登録(する)d module. If sal_True is returned then osl_unloadModule is called for the belonging module as often as it is 登録(する)d.

A call to osl_unloadModule does not 保証(人) that the module is 荷を降ろすd even if its component_canUnload 機能(する)/行事 returns sal_True.

The optional in-parameter libUnused 明示するs a period of time which a library must be 未使用の ーするために qualify for 存在 荷を降ろすd. By using this argument one can 反対する the multithreading problem as 述べるd その上の above. It is in the 責任/義務 of the 使用者 of this 機能(する)/行事 to 供給する a timespan big enough to 確実にする that all threads are out of modules (see component_canUnload).

The service 経営者/支配人s which have been created by 機能(する)/行事s such as createRegistryServiceFactory (宣言するd in cppuhelper/servicefactory.hxx) are 登録(する)d listeners and 解放(する) the 言及/関連s to factories on notification.

Parameters
libUnused
(期間が)わたる of time that a module must be 未使用の to be 荷を降ろすd. the 
argument is optional.

rtl_unregisterModuleForUnloading
extern "C"
無効の rtl_unregisterModuleForUnloading(
oslModule module );

事実上の abstract const volatile template static inline C-結合,連鎖
NO NO NO NO NO NO NO YES

Description
The 機能(する)/行事 取り消すs the 登録 of a module. By calling the 機能(する)/行事 for a 以前 登録(する)d module one 妨げるs the module from 存在 荷を降ろすd by this 荷を降ろすing 機械装置. However, ーするために 完全に unregister the module it is necessary to call the 機能(する)/行事 as often as the module has been 登録(する)d.

rtl_unloadUnusedModules unregisters the modules which it 荷を降ろすs. Therefore there is no need to call this 機能(する)/行事 unless one means to 妨げる the 荷を降ろすing of a module.

Parameters
module
a module 扱う as is 得るd by osl_loadModule

最高の,を越す of Page

Apache Software Foundation

Copyright & License | Privacy | 接触する Us | 寄付する | Thanks

Apache, OpenOffice, OpenOffice.org and the seagull logo are 登録(する)d trademarks of The Apache ソフトウェア 創立/基礎. The Apache feather logo is a trademark of The Apache ソフトウェア 創立/基礎. Other 指名するs appearing on the 場所/位置 may be trademarks of their 各々の owners.