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 mme...@openoffice.org Tue Apr 7 09:27:09 +0000 2009 ------- Hi Kay; > You really don't want to change code because a component is suddenly > needed during start-up, do you ? Sure you do - you want to change the code that uses it, so that it does not anymore :-) this is in fact exactly what I want to catch, regression wise. Currently the only real way to catch these regressions is to re-profile the application regularly, and spot the obvious sillies - this (as we have seen) is by no means a reliable way of stopping things creep in. We get slower by mistake, all over the place. > IMHO a component author should not make assumptions about "when" a > component is needed ... ideally people would just follow that > late-init paradigm while programming. Ideally, of course - however; in the stark light of day - we have had the whole database engine accidentally initialized during startup via some accidental change somewhere, that forced something to be inited earlier than it was expected to be, that causes a substantial performance problem - and this is by no means an isolated case. Having a decent set of assertions to ensure that code doesn't creep into the startup path would be extremely useful. The assertion could be as simple as just printing something on the console under Unix; "This should not happen <filename>" or something, it doesn't have to abort() - just that would bring it to people's attention quickly. All it requires is some rather low-level module [ sal ], to incorporate the relevant assertion macro & method call - hence the request for an elevated Sun architect's input. --------------------------------------------------------------------- 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: issues-unsubscr...@lingucomponent.openoffice.org For additional commands, e-mail: issues-h...@lingucomponent.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
