Sorry, guess I must be reading the help all wrong.

Just FYI to follow up on this post and especially the quoting issue. A few months ago I decided to use TCC to code the back end of a small web project, fronted by the Abyss server. It is not too difficult for the most part. I've coded quite a bit of php, and contributed code to the haserl...

That probably should be more clearly documented in the help. I've used this since the first Norton version and never understood that behavior -- probably because I never had need until now to shift between multiple modes, only to disable some and then /X0.

Latest TCC version. No problems with SETDOS from the command line. From within a BTM: set XSTR=-245689A setdos /x%XSTR setdos and then later: set XSTR=-24689A setdos /x%XSTR setdos After the first setting, setdos will show EXPANSION=245689A After the second, setdos will still show...

Separate control over piping in SETDOS /X The /X5 option lumps piping in with multiple and conditional commands. There are times when I need piping but would benefit from being able to disable the other parts.

http://jpsoft.com/forums/showthread.php?t=1004 http://jpsoft.com/forums/showthread.php?t=1152 http://jpsoft.com/forums/showthread.php?t=1148 http://jpsoft.com/forums/showthread.php?p=1149 http://jpsoft.com/forums/showthread.php?t=1214

No, that is not the same. Using setlocal/endlocal to bracket a sub effectively kills the ability to set any global vars. Yes, it will do if you want absolutely everything local, but it is not the same as being able to explicitly define local vars.

No. The command prompt wouldn't require an option. Many other scripting languages, especially in the *nix space, will accept a script on stdin. If you try that with tcc, it literally tries to feed the command line from stdin. That's not the same as running a script, as evidenced by the...

Yeah, I gathered that. Too bad. Sometimes limitations are, well, limiting :-) There needs to be a startup option that tells tcc to use the supplied file as a BTM, regardless of extension. Something like: tcc.exe /b filename.anyext And since the wishing well is open, it would be VERY nice...

I want to be able to execute BTM files, but with an extension of .tc instead of .btm, under XP/Vista. I tried associating the ".tc" with "%COMSPEC /i /d /c", but I get an endless loop of tcc subshells, never any output from the script. Yes, the script works fine as a .btm, just to intercept...

I think having to remember to %@UNQUOTE throughout your code is in itself a form of checking.

Okay, I'm probably the only person in the world using TCC to write back end website code, but... %@hexencode[{"chars",}string] => convert all characters other than [0-9A-Za-z+_=&-] to %xx hex notation, with the option to specify a list of characters to convert %@hexdecode[{"chars",}string]...

Just because it WAD doesn't mean AD is the best it can be :-) No, I expect %3 to include only %3. However, I DO expect %3$ to include %4 - %n. So why not allow %pvar$, when %pvar is the last parameter of a gosub, to behave the same? That would be a NEW convention would break NO existing...

I didn't see this anywhere, but forgive me if I simply missed it. I would like to request this: Local Variables in Gosubs This is almost already present, in that Gosub parameter variables are local to the sub. However, there's no way to define them except in the :Sub definition. An example...

The help for tc10 states that: :Sub1 [str n world] when called with: Gosub Sub1 abc 15 "Hello World" will result in str=abc n=15 world="Hello World" This is fine. I love gosub vars. Furthermore, if the sub is called with: Gosub Sub1 abc 15 that results in: str=abc n=15 world=...