Difference between revisions of "Uno/To-Dos"
From Apache OpenOffice Wiki
< Uno
m |
m |
||
Line 17: | Line 17: | ||
* Consolidate "uno_Environment" with "uno_ExtEnvironment". | * Consolidate "uno_Environment" with "uno_ExtEnvironment". | ||
* remove "#ifndef EXCEPTIONS_OFF" macros | * remove "#ifndef EXCEPTIONS_OFF" macros | ||
+ | * SAL_CALL really necessary for "inline" stuff? | ||
Features | Features |
Revision as of 13:29, 7 April 2006
ToDos and potential ToDos
module naming
- rename cppu -> binary uno
- rename cppuhelper -> cppu
clear separation between C and C++
- move C++ stuff from cppu to cppuhelper
simplification / performance
- remove
uno_Interface
and friends, replace with one of the platform C++ ABIs - support direct access of UNO types in IDL, without includes
- let the *makers retrieve type information from the type providers and not from rdb files
- harmonize initial object access for "remote" and libraries, it is actually the same
- leverage purpose environments for global variables, e.g. the "ServiceManager" or the "ComponentContext"
- Remove all exception specifications.
- Consolidate "uno_Environment" with "uno_ExtEnvironment".
- remove "#ifndef EXCEPTIONS_OFF" macros
- SAL_CALL really necessary for "inline" stuff?
Features
- introduce process lifecycle based on living threads
- have UNO package support for the URE
- move the UCB into the URE
- move the configr mgr. into the URE
- alien type support e.g. for Java
General
- standardize?