- May
- 3,515
- 5
I think of output-only programs as having a one-way interface. AFAIK in any version of WindowsNT+ every window is inherently a two-way interface, but the application using it need not accept input through the window.
---------
HELP explicitly states that
1/ the BDEBUGGER command is for editing and debugging TCC programs (batch files), and
2/ the IDE command is for editing text files, with special features for certain scripting languages.
As my previous post stated, IMHO the IDE comand does not require a text window per se just for editing. However, the TCC implementation - possibly due solely to Windows API limitations - may require the use of such a window. It would not bother me the least.
To me it is more bothersome that arrays are not inherited in the TCC instance which BDEBUGGER starts. I would like to see a clear list of which TCC features are and which are not inherited: arrays, binary buffers, open file handles, open XML, etc.
---------
HELP explicitly states that
1/ the BDEBUGGER command is for editing and debugging TCC programs (batch files), and
2/ the IDE command is for editing text files, with special features for certain scripting languages.
As my previous post stated, IMHO the IDE comand does not require a text window per se just for editing. However, the TCC implementation - possibly due solely to Windows API limitations - may require the use of such a window. It would not bother me the least.
To me it is more bothersome that arrays are not inherited in the TCC instance which BDEBUGGER starts. I would like to see a clear list of which TCC features are and which are not inherited: arrays, binary buffers, open file handles, open XML, etc.