How to? start up switches

[fpefpe]

Hello — I been running an old win10 32bit system as a vm and came across this issue — I have take v19 (long past it EOL but still works for me) and was running it as a stand-a-lone program with the switches
"/is /ix /ii /ip /q /c” so that it would run just 1 internal command and I would then capture the output of it. What I found out is that these switches for most part stop the default start up, but in this case the plugins were still auto-loaded from the plugins folder.

I check with the help/doc and it seems that /I is the parent option and the the other are specific to what to turn-off when tcc starts. So I changed the switches to just “i /q /c" and this setting stopped the plugins from loading.

Not sure if this is a bug, and I know its version 19 but should both sets of switches work the same way?

 

[epement]

If TCC v19 has an /ip option switch to prevent the loading of plugins, I anticipate that it ought to work regardless of where the switch occurs on the command line. However, maybe its placement on the command line affects how or when it loads.

I agree with you that both sets of switches ought to work the same way, but since this is such an old version of TCC and is not distributed anymore, there is no incentive to fix it.

 

[Charles Dye]

I just tried the experiment, and I can reproduce this in the current v36. It looks like /IP must precede any of the other /Ix options on the command line:

start /pgm %_cmdspec /ip

disables automatic loading of plugins, but

start /pgm %_cmdspec /il /ip

does load plugins.

I would say that this does constitute a bug, though an obscure one. Using /I to disable all startup features at once seems like a pretty good workaround. I can't speak for Rex, but I would guess that this may get fixed in v37. Version 19, fuhgeddaboudit.

 

[Jay Sage]

At the very least, the help file should be updated. I just looked at it, and the discussion is rather vague when it comes to the /I switch. For the command line, the expression /i[ipsx] is used (in caps, and with L missing). That could be interpreted to mean that after /i one can include any collection of zero or more of those four (should be five) letters, such as /iip of /ipsx.

In the more detailed description for the /i switch, the help says that one can specify individual arguments (and includes five such arguments: ILPSX). It does not say whether one can have multiple /i switches.

I tried running

start /pgm "C:\Program Files\JPSoft\TCMD36\tcc.exe" /ip /is​

and the /ip switch was processed but the /is switch was ignored. If I run

start /pgm "C:\Program Files\JPSoft\TCMD36\tcc.exe" /ips​

then plugins are not loaded and tcstart does not run. Ditto for the switch /isp. It looks as though my initial interpretation is correct: a single /i switch followed by any collection (including none) of the individual options.

 

[fpefpe]

I knew that there was no fix for v19 but as noted v36 does have this issue --- at best it should documented that /ip should be the first switch in the list if specified

 

[Jay Sage]

at best it should documented that /ip should be the first switch in the list if specified

As I think that I demonstrated above, that is not sufficient. It appears that there can be at most one /i switch. If one wants to specify multiple options, they should all be appended to the single switch expression.

 

[rconn]

You cannot specify multiple /Ix options. If you want to turn multiple options off, use the /Ixxx format.

I will make this clearer in the help.