0
$\begingroup$

I came across this description of Batch Interface: "commands and directives are used to manage those commands that are entered into files and those files get executed. "

I would really appreciate if someone explains in detail what Batch Interface is and how it's different from Command Line Interface?

$\endgroup$

closed as off-topic by David Richerby, dkaeae, xskxzr, Evil, Discrete lizard Aug 30 at 15:38

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question does not appear to be about computer science, within the scope defined in the help center." – David Richerby, xskxzr, Discrete lizard
If this question can be reworded to fit the rules in the help center, please edit the question.

  • $\begingroup$ Some people would call it a "script". If you've ever used Linux, you'll get the difference in a second. $\endgroup$ – dkaeae Aug 20 at 7:41
0
$\begingroup$

In the olden days, you wrote up a sequence of operations to be executed (typically on punched cards, a job), and handed them to the operator to be loaded. The operating system took such a batch of commands to execute off it's input queue, ran them until the end (or something failed), and took the next one. Output was collected (probably printed out) to return to you.

If the above is what is meant, the crucial difference is that in batch processing you get (perhaps the next day) the feedback that the job failed because of a syntax error or some equally irritating glitch. With a command line interface you run one command, can check it's output or correct the command before entering the next one.

$\endgroup$

Not the answer you're looking for? Browse other questions tagged or ask your own question.