<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - The ImplementationName "com.sun.star.comp.math.FormulaDocument was changed to upper case "M" in ".Math." New incompatibilities!" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111811#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - The ImplementationName "com.sun.star.comp.math.FormulaDocument was changed to upper case "M" in ".Math." New incompatibilities!" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111811">bug 111811</a> from <a class="email" href="mailto:jag@psilosoph.de" title="Wolfgang Jäger <jag@psilosoph.de>"> Wolfgang Jäger</a> <pre>(In reply to Maxim Monastirsky from <a href="show_bug.cgi?id=111811#c9">comment #9</a>) > (In reply to Wolfgang Jäger from <a href="show_bug.cgi?id=111811#c8">comment #8</a>) > > But: If the names of services and interfaces also are "subject to change" > > under something like the above quoted statement by Stephan Bergmann, how > > should someone write long-term-reliable code ("3rd-party") for special > > requirements or for a distributable extension? > Just to clarify: Names of services and interfaces are not "subject to > change", only implementation names are. ... Thank you very much. This clarifies the situation for me. I didn't know a specification to that effect. However, what I need to know are the services. And in by far the most cases I tested for service support. Then there was an exception... > ... That is, checking with > supportsService is the right thing to do, and is what was guaranteed to stay > compatible across versions. Would you mind to tell me where the "guarantee" is given?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>