11-22-2023, 01:46 AM
It reminds me of what little I read of the REXX processor in OS/2. :/
Could have code like this (sorry not familiar with this "batch" language):
Then "hello" would stop printing "hello" and instead the value of the variable of the same name. But I'll bet that was hell to parse for whoever created the "batch" language.
It must have required two or more passes, which I don't think was how the MS-DOS batch file processor worked. If not then be forced to look at every single token (except keywords and operators) to see if it happened to be a variable. (shrugs)
To scan something like this:
would require some kind of preprocessor, or at least one extra pass only to pick up "special" variable names. Might as well allow also symbols like dollar sign and ampersand to be the first character of an identifier in that case. The problem with that is it would make compilation even slower, which is not tolerated very much except with C/C++ only because that is ubiquitous.
Could have code like this (sorry not familiar with this "batch" language):
Code: (Select All)
hello = 4
SAY hello everyoneThen "hello" would stop printing "hello" and instead the value of the variable of the same name. But I'll bet that was hell to parse for whoever created the "batch" language.
It must have required two or more passes, which I don't think was how the MS-DOS batch file processor worked. If not then be forced to look at every single token (except keywords and operators) to see if it happened to be a variable. (shrugs)
To scan something like this:
Code: (Select All)
DIM 20D AS LONG
20D = 50
A = 20Dwould require some kind of preprocessor, or at least one extra pass only to pick up "special" variable names. Might as well allow also symbols like dollar sign and ampersand to be the first character of an identifier in that case. The problem with that is it would make compilation even slower, which is not tolerated very much except with C/C++ only because that is ubiquitous.