v27.00.16/17: ENDLOCAL with exporting variables wipes out the complete Environment

[Peter Murschall]

include %PATH%
T1.BTM

Echo Test for Setlocal/EndLocal
:Set Directory-List
Set dirlist=E:\Projekte,E:\Daten\Excel
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Echo %0 : dirlist before: %dirlist%
Call T2.btm
Echo %0 : dirlist after:  %dirlist%
Echo %0 : tempVar after Endlocal:%tempVar%
Pause

T2.BTM

SetLocal
  Set tempVar=Hello !!
  Echo %0 : tempVar:%tempVar%
  Echo %0 : Environment before ENDLOCAL 
  Set
EndLocal tempVar
Echo %0 : tempVar after ENDLOCAL:%tempVar%
:
Echo %@REPEAT[*,%@DEC[%_COLUMNS]]
:
Echo %0 : Environment after ENDLOCAL
Set
Echo %@REPEAT[=,%@DEC[%_COLUMNS]]

 

[vefatica]

Here's a simpler example.

 

[Joe Caverly]

Same thing here, and, when I run the following command;

[E:\Utils]wsl file subnet.exe
The COM+ registry database detected a system error

I was wondering why I started getting that error.

I have a .BTM that has;

endlocal path hb_compiler

and it indeed exports both environment variables, but the environment before the .BTM is gone.

I just tested with V26, and works as it should.

Joe

     _x64: 1
   _admin: 1
_elevated: 1

TCC  27.00.17 x64   Windows 10 [Version 10.0.18363.1256]