Slashdot Mirror

← Back to Stories (view on slashdot.org)

For Automated Testing, Better Alternatives To DOS Batch Files?

Posted by timothy on from the run-them-under-wine dept.

An anonymous reader writes "I am working on a project that would allow our customers to test out sending different PCL commands to LAN printers. My initial thought was that a DOS batch file will allow users to select some simple options, send the tests to printers, and even generate a small web page which, when launched from the batch file, will provide email feedback on the tool. This all worked. To spice it up I added some ANSI color commands to the menus, though the implementation of that may prove tricky without resorting to .COM files or forcing the load of the ansi.sys via the command.com shortcut. And this implementation goes against my initial idea that I want the entire thing to be contained in a standalone batch file. My questions are: Is there a better option for this? Are DOS Batch files too 1990s to be taken seriously in 2010? The application needs to (1) be simple (2) be easy to update (3) be able to send PCL commands to LAN-attached printers and (4) allow email feedback. I don't know what other programming language would allow this and be as simple. I tend to think that I have found the best tool for the job but if you have another idea let me know. Call me crazy but I love DOS."

4 of 426 comments (clear)

  1. Re:perl? by steveg · · Score: 4, Interesting

    Even better Strawberry Perl

    --
    Ignorance killed the cat. Curiosity was framed.
  2. Powershell by Shados · · Score: 4, Interesting

    The modern way of doing shell scripting in Windows is now powershell, and most things are quickly moving toward that. Its not as integrated in the OS, but its damn close, and in many ways its better than alternative scripting languages (object piping instead of text piping, for example).

    Now if its the best thing for your requirement? I don't know. But if you're planning to stick to shell scripting, do yourself a favor and upgrade.

  3. Try Windows PowerShell by UTF-8 · · Score: 3, Interesting

    DOS batch files has too many limitations when compared to other scripting languages. It's frozen in time. I consider Windows PowerShell to be the batch file successor.
    http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx

  4. Re:perl? by Anonymous Coward · · Score: 3, Interesting

    You can cut the bloat by making the executables dependent on an external perl5lib.dll file. You can also factor out common libraries into separate PAR packages to be used by your executables. But this blows the whole point of bound exes in my opinion, and disk is cheap.