Slashdot Mirror
For Automated Testing, Better Alternatives To DOS Batch Files?
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."
DOS Is dead use visual basic
You're crazy.
Freedom is the freedom to say that 2 + 2 = 4
Is Ed "Too-Tall" Jones too tall?
I believe the only sensible and practical idea here is to have 1000 monkeys at 1000 consoles doing these automated tasks for you. Of course you'd need to feed these monkeys, so you'd need more monkeys. Thus, 1000 monkeys at 1000 banana plantations.
"I'm going to f***ing bury that guy, I have done it before, and I will do it again. I'm going to f***ing kill Google"
DAWS.
No, the S is soft as in "esss" not "zee". da "AWE" ssss
It's pronounced the same as the word "DAS" in German; the A is soft ("AAAH" not "OH")
So... "DAHS" is probably about right.
And since no decent /. Anon post is complete without some kind of rant:
The word is wash. Observe the letters, notice you have Waaaaaaaaaa and then sshhhhhhhhh.
There is NO 'R' in wash.
It is not pronounced WORSH otherwise it'd be spelled that way.
It's not a regional accent, it's a complete mis-pronunciation of the word. Stop it already; it just makes you sound like you have a speech impediment. Or a single digit IQ.
I am working on a project that would allow our customers to test our sending different PCL commands to LAN printers.
I will be looking forward to the first error is encountered by a user. You will hear someone in the cubical farm say, "PCL PC Load letter? What the fuck is PCL PC Load letter?!?"
HA! I just wasted some of your bandwidth with a frivolous sig!
As you seem to be a MS fan, I can't believe you didn't consider dotNet languages and Silverlight.
My personal favorite is VB.Net.
Massive executables are the best way to show that your tool is of professional quality.
Silverlight is of course necessary for any kind of interface.
If you want to avoid a Web interface, use XAML.
Hey, we are in 2010 !
Wizard? Pfft!
He needs to re-implement Clippy!
Think of how helpful this would be :)
...
The other posters are correct. You only say "DAHS" if you're from Boston, as in: "Oh My Gawhd, some retahd on slashdaht is still writing DAHS bahtch files. Why don't we just fihre up Windows fah Workgroups while we're aht it."
Seriously though - I think nmap can send PCL commands via the nmap scripting engine, which is written in LUA. How about wrapping that with what some of the other posters are suggesting?
You can just make an exe out of a python script which collects the runtime and all dependencies into a single file. I'd want to do that before resorting to invoking VB. I guess if it is an all-MS shop locked in some sort of hellish time vortex (which is consistent with the OP asking about batch files) then they may keep enough Eye of Newt and pentagrams handy to make VB seem like a convenient option.
That's me Perl hardcore programmer saying.
If your Perl code is anything like your sentences...oh, who am I kidding, it would still make more sense than MY Perl code.
You can use bash on most Linux implementations
You're in luck: there is something better than being a trolling twat making useless suggestions. It's called "sticking your head in a vise."
What you do is get a vise, you put your head in it, and you twist the handle until it contacts both sides of your head. At this point you'll really have to turn the handle hard, but keep going.
You can stick your head in a vise in most wood shops.
I write Perl largely like I learned to write C, so its very readable, though perhaps not particularly idiomatic.
woorsh?
Yeah. VB, C++, Java, they all do PCL commands.
..but will it fit on a floppy ??
I never heard anyone say it.
Ugh. Now I feel old. Screw you, AC.
A novice had a problem and could not find a solution. "I know," said the novice, "I'll just use Perl!" The novice now had two problems.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
I'll second this one. The place that I work runs almost all of its commands via bat jobs that run from simple to complex. When I started here, I installed Strawberry Perl on my win32 system. I have, since, replaced every functionality that the bat jobs used to do with perl scripts (primarily for my own purposes, but most of my coworkers don't mind them either). The primary reason I did this was readability.
That's the first time I've heard Perl and better readability together.
The moderators are having a field day with this one.
That's the first time I've heard Perl and better readability together.
He did say they started out as bat files...