TCC started with /I but still have _TCEXIT

[vefatica]

After startng with /i (Run dialog), _TCEXIT is set. It is not executed.

TCC  36.00.51 x64   Windows 11 [Version 10.0.26200.8457]
Copyright 2026 JP Software Inc.  All Rights Reserved
Registered to JJ

v:\> echo %@wmi[.,"Select CommandLine from Win32_Process where ProcessId=%_pid"]
d:\tc36\tcc.exe /i

v:\> echo %_ininame %_tcstart %_tcexit
  D:\tc36\TCEXIT.btm

 

[Alpengreis]

Is /i not that here?

/I Don't load the .INI file, execute TCSTART or TCEXIT, or load plugins. You can optionally specify individual arguments

 

[vefatica]

If it will not be executed, the variable should not be set.

 

[rconn]

WAD, and 20+ year old behavior. I am not going to make a breaking change at this point.

The file still exists, even if you're not executing it.

 

[vefatica]

WAD, and 20+ year old behavior. I am not going to make a breaking change at this point.

The file still exists, even if you're not executing it.

Could say the same for TCMD.INI and TCSTART.BTM. What would it break?

 

[rconn]

Could not say the same for TCMD.INI and TCSTART.BTM, because they have already been processed (and disabled). To do it for TCEXIT as well requires the quantum computing version of TCC, so it can travel into the future to see whether TCEXIT is going to processed.

A better question than "What would it break?" for long (long, long) existing behavior is "What benefit would it provide, given there is a non-zero chance it will break things?"