To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=66635
------- Additional comments from [EMAIL PROTECTED] Mon Nov 13 06:19:36 -0800 2006 ------- Sorry, sb, I had not understand you before. The issue with the current method of obtaining a XIdlClass from a Type is that it is unnecessarily complex. It is against common sense that one should obtain the name of a type, and then obtain a XIdlClass from it. It makes the developer spend time looking for a different way, since one thinks "it is not likely that this is the intended way". The complexity added is minimal. The method implementation is a one-line. The real issue is not so much performance as it is cleanness, maintainability and simplicity. If one reads code Reference<XIdlClass> t_refl = core_reflection->forType(t); then the code expresses perfectly the intention of the developer. >From the performance point of view, the current method goes from a type to a name, and then CoreReflection::forName() goes from the name to recover the original type. Although It is not necessary to make a benchmark to know that it cannot be optimal, the added implementation complexity is more important than speed. --------------------------------------------------------------------- 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]
