Category talk:DOS Batch File
Rename the language
While the roots of this language lie with DOS (and CP/M before that) most of the programs featured on this site can't possibly work in DOS since they're using functionality introduced with cmd.exe in Windows NT. For that reason the name "DOS Batch File" is pretty misleading and should be changed. --Johannes Rössel
- What should it be? --Mwn3d 18:31, 27 August 2009 (UTC)
- Windows Batch File might be an appropriate alternate name --Johannes Rössel 18:39, 27 August 2009 (UTC)
- Or just Batch File. After all, there are not many systems nowadays using that term. Similarly to how "shell scripts" generally refer to a UNIX-like CLI environment. —Johannes Rössel 18:56, 27 August 2009 (UTC)
- Well, depends if you're writing for 98-era COMMAND.COM or XP-era CMD.EXE, as the languages have a huge number of differences, rather like the difference between BCPL and C in scale though not detail. (I've done a fair bit with both types of batch file, but don't want to revive the experience. My windows systems now have bash installed…) Given that, someone needs to evaluate what language the existing examples are actually written in and work out what the renaming should be to. —Donal Fellows 21:18, 27 August 2009 (UTC)
- Well, for me it's fine to have both. I've seen insane things being done in (actual) DOS batch files and I think some problems may well be solved in it, though for me it's a rather lost art and I am only proficient in the cmd.exe variant of the language. As for the existing examples (there aren't that many anyway), Basic integer arithmetic and Command line arguments are currently in the Windows flavor, the other four (File creation [incomplete], File exists [incomplete], File rename [potentially incomplete] and Walk directory tree [likely wrong]) should (I'm not entirely sure, though) work in plain command.com. Command line arguments can be redone in a cleaner and command.com-friendly manner, though. So apparently there is much to cleanup anyway and not that many complete and correct solutions remain (provided my initial thoughts on their correctness are, in fact, correct). —Johannes Rössel 21:32, 27 August 2009 (UTC)
- Well, depends if you're writing for 98-era COMMAND.COM or XP-era CMD.EXE, as the languages have a huge number of differences, rather like the difference between BCPL and C in scale though not detail. (I've done a fair bit with both types of batch file, but don't want to revive the experience. My windows systems now have bash installed…) Given that, someone needs to evaluate what language the existing examples are actually written in and work out what the renaming should be to. —Donal Fellows 21:18, 27 August 2009 (UTC)