| Line 31... |
Line 31... |
| 31 |
When SvarCOM executes a command, it checks first if it has a *.BAT extension.
|
31 |
When SvarCOM executes a command, it checks first if it has a *.BAT extension.
|
| 32 |
If so, it switches into 'batch-processing' mode:
|
32 |
If so, it switches into 'batch-processing' mode:
|
| 33 |
|
33 |
|
| 34 |
- Writes the batch filename into its persistent (rmod-owned) buffer, along
|
34 |
- Writes the batch filename into its persistent (rmod-owned) buffer, along
|
| 35 |
with a counter that holds the offset of the next line to be executed.
|
35 |
with a counter that holds the offset of the next line to be executed.
|
| 36 |
- When a batch file CALLs another batch file, then a new SvarCOM instance is
|
- |
|
| 37 |
started. This ensures that once the CALLed batch ends, processing will
|
- |
|
| 38 |
return to the original batch file at the correct position.
|
- |
|
| 39 |
|
36 |
|
| 40 |
When the batch buffer is non-zero, SvarCOM does not ask the user for a
|
37 |
When the batch filename buffer is non-empty, SvarCOM does not ask the user for
|
| 41 |
command. Instead, it opens the batch file, jumps to the "next line to be
|
38 |
a command. Instead, it opens the batch file, jumps to the "next line to be
|
| 42 |
executed" and loads the command from there, incrementing this counter in the
|
39 |
executed" and loads the command from there, incrementing the line counter in
|
| 43 |
process.
|
40 |
the process.
|
| 44 |
|
41 |
|
| 45 |
|
42 |
|
| 46 |
====================================================================== EOF ===
|
43 |
====================================================================== EOF ===
|