<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><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#c9">Comment # 9</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 <span class="vcard"><a class="email" href="mailto:momonasmon@gmail.com" title="Maxim Monastirsky <momonasmon@gmail.com>"> <span class="fn">Maxim Monastirsky</span></a>
</span></b>
<pre>(In reply to Wolfgang Jäger from <a href="show_bug.cgi?id=111811#c8">comment #8</a>)
<span class="quote">> 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?</span >
Just to clarify: Names of services and interfaces are not "subject to change",
only implementation names are. That is, checking with supportsService is the
right thing to do, and is what was guaranteed to stay compatible across
versions.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>