| Re: [cdt-dev] Variable name of USER:CONFIG environment goes to uppercase |
Martin
The way I understand it: In your case CDT enforces you to use
uppercase for all your environment variable names. Both in
declaration and usage.
The declaration is automagically, the usage is up to you.
My plugin Sloeber contains code to hunt down the usage of
environment variables in environment variable values to convert
them to upper case. I think because I have been using a
cygwin/mingw make. I just can't imagine I bothered writing this
code if it would have worked without it (but I've been wrong
before).
If the environment variables were only usable in the windows os (Which may have been the case at the time of the workaround implementation) the hunting down would not be needed.
Best regards
Jantje
Am Fr., 22. Mai 2020 um 17:50 Uhr schrieb Jonah Graham <jonah@xxxxxxxxxxxxxxxx>:
There are a number of cases that it is supposed to workaround, main one that comes to mind is that Path vs PATH on Windows refers to the same environment variable - so it seems that the assumption is on windows the case of the environment variable was not supposed to matter and so normalizing them to all uppercase made sure that Maps in java worked as expected.
What will be the effect of this uppercasing, if Eclipse is running on windows but the *built* runs in a docker container (which always is linux) IIRC?Martin
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev