Batch is a programming language. You are wrong. Suck it up.
Thank you for the links. They say what I said, BATCH is NOT a language.The references are to the use of the command interpreter, which has a its own language.
American is not a language.
European is not a language.
ASNII(ANSI?) is not a language.
Batch is not a language. It is a BATCH.
American is a dialect of English(generally referred to as "American-English",but reference to the "American" language is common as well, especially among English speakers), in that it is a variant of the "queen's English" which in and of itself is likely a variant of Saxon tongues. This type of heirarchy occurs with Programming languages as well, for example- C branches of to C++, and Java can be said to root in both Visual Basic and C. The fact that any Real-life language is merely a dialect of some other previous vernacular makes it no less of a language.
the Windows/MS-DOS command-line is the only one whose programmatic entity is referred to as a "Batch Program" within standard vernacular. you don't here people refer to Bash Batch files or Bourne Batch files. they are called scripts. And they are referred to as Programming, if only at the highest OS level by those who write them and the linux community in general. Nobody in the Linux community would likely oppose calling these "scripts", even if it implies "programming". Which brings up yet another question. If it isn't actually "batch programming" but rather "command-line" programming, why is it that "Visual Basic Programming" or "C Programming", both being comprised of the creation of
Batches of Statements in that particular language, aren't called "Batch Visual Basic " or "Batch C"? Because the ability to have blocks of statements execute sequentially is defined in the language itself. In a similar vein, since Batch files allow for the use of parentheses for grouping and other commands that aren't possible to use at the command-line, it is thus a superset of the command-line itself, and thus it cannot be referred to as simply a "batch" of commandline language statements, as it defines it's own constructs not available at the command-line.
Of course, this definition means that Pre-NT DOS batch programming was not programming either- however, it was. Since, according to the definition of "programming language":
A programming language is a machine-readable artificial language designed to express computations that can be performed by a machine, particularly a computer. Programming languages can be used to create programs that specify the behavior of a machine, to express algorithms precisely, or as a mode of human communication.
"Batch" meets all of what this definition states, in all it's forms. And despite what I believe might be your main proposal, calling it "Batch programming" is not ambiguous to other command-line implementations of what a "Batch" is in DOS/Windows simply because those shells refer to their implementation of Batch programming as "Scripting"... Scripting is a form of programming and since this is essentially an implementation of similar functionality from Batch, batch is thus also "batch Scripting"... Scripting is programming.
HTML, SGML, XML, etc. While not introduced in this discussion, do not meet the requirements of being a programming language. They are used to define how data is displayed, but do not provide the actual algorithms for how the display parameters are to be met. As an example, the <HR> tag creates a hard rule section break on a HTML page. While you can change the properties used to draw that rule (such as size, Color, etc) there is no definition of how those properties are to be applied to create a section break, since that logic is within the web browser. In a similar vein, batch programming does both- it can invoke other applications and commands to perform particular tasks with specified parameters, or it can be used to create the logic behind such commands.
COMMAND line programming is programming in the command line language.
References to BATCH programming are short forms of reference to doing command line programming using a file that contains the script the COMMAND program will interpret.
