1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-24 17:35:35 +02:00

Bug 560330: Document \$ escaping change in API doc

This makes it consistent with how environment variable uppercasing
was documented as they are similar.

Change-Id: I580f599e77db08285753d47c62f46120abd8f9bd
This commit is contained in:
Jonah Graham 2020-08-31 09:28:13 -04:00
parent a83e8924ba
commit 78c7962787

View file

@ -45,6 +45,7 @@
<li><a href="#optionsAPI">Removal of CDT Core Options API.</a></li>
<li><a href="#terminal">TM Terminal has major changes to support new color and preference functionality.</a></li>
<li><a href="#casesensitive">Environment Variables are always case sensitive in CDT.</a></li>
<li><a href="#escaping">Environment variables no longer support \${ to avoid expanding.</a></li>
</ol>
<p>
Planned Removals after June 2022
@ -285,6 +286,19 @@
<li>org.eclipse.cdt.core.envvar.IEnvironmentVariableManager.isVariableCaseSensitive() removed.</li></li>
</ul>
<h3>14. <a name="escaping">Environment variables no longer support \${ to avoid expanding.</a></h3>
<p>
This change is not literally an api change but will impact your code if you used \${ to not
expand environment variables. It may impact your code if you import environment variables
and had to workaround path\${childPath} resolving to path${childPath}. See <a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=560330" target="_blank">Bug 560330</a>.
</p>
<ul>
<li>org.eclipse.cdt.managedbuilder.core.IBuilder.isVariableCaseSensitive() removed.</li>
<li>org.eclipse.cdt.managedbuilder.envvar.IEnvironmentVariableProvider.isVariableCaseSensitive() removed.</li>
<li>org.eclipse.cdt.core.envvar.IEnvironmentVariableManager.isVariableCaseSensitive() removed.</li></li>
</ul>
<hr>
<h2>Future Deletions</h2>