From 78c7962787885e692da2266c76577c95449a6c28 Mon Sep 17 00:00:00 2001 From: Jonah Graham Date: Mon, 31 Aug 2020 09:28:13 -0400 Subject: [PATCH] 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 --- .../guide/deprecated_API_removals.html | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/org.eclipse.cdt.doc.isv/guide/deprecated_API_removals.html b/doc/org.eclipse.cdt.doc.isv/guide/deprecated_API_removals.html index 28aa81029c7..1578ac3e565 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/deprecated_API_removals.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/deprecated_API_removals.html @@ -45,6 +45,7 @@
  • Removal of CDT Core Options API.
  • TM Terminal has major changes to support new color and preference functionality.
  • Environment Variables are always case sensitive in CDT.
    • +
  • Environment variables no longer support \${ to avoid expanding.

    • Planned Removals after June 2022 @@ -285,6 +286,19 @@

  • org.eclipse.cdt.core.envvar.IEnvironmentVariableManager.isVariableCaseSensitive() removed.
    • +

    14. Environment variables no longer support \${ to avoid expanding.

    +

    + 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 Bug 560330. +

    + +

    Future Deletions