To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=100757
------- Additional comments from [email protected] Tue Apr 7 10:51:40 +0000 2009 ------- Michael, let me just think loudly ... On the one hand we want to avoid that a library becomes loaded / initialized etc. during start-up, just because a service is mentioned somewhere. On the other hand we also want to avoid scattering code over the whole office, checking if a reference is valid, to than instantiate the wanted service. Actually, this could be achieved by simply extending e.g. the Uno Reference class to support on-demand instantiation, the moment an object is needed it becomes created ... This does not address the issue, that anybody may retrieve an object to do something, which could be done later. The overall underlying problem is the fact, that the start-up has been programmed explicitly, by sequence of statements creating this, initializing that, all under the assumption, that the author knows the dependencies. I think every reasonable experienced engineer does know how to do this start-up thing right, though most just try to fetch some low hanging fruits, avoiding some bigger refactorings. We may want to utilize the suggested helper assertions, though I feel / fear, that this "hack" would never become removed again ... Kay --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
