What Winbatch Can and Can't DoKeywords: What Winbatch Can and Can't Do
Question:Being one interested in things REALLY good, was just wondering whether it would be worthwhile having a list of "stuff" that Winbatch cannot do. In reading posts, there has been a number of queries that ask "How can I convert from this product or that product to Winbatch?..because I prefer Winbatch" Appears to me that there is not much that Winbatch cannot do in terms of products of a similar ilk. Perhaps it might be worthwhile collating those "few" things that it cannot do as a quick reference for your users.
WinBatch cannot Run from DOS. It needs to run from Windows.
It runs only "iffy" on a MAC with PC emulation software.
It is not intended for "computationally intensive" calculations such as deriving prime numbers and other NP-Hard sort of academic computational problems.
Although originally designed as a utility-only lanugage, continuing improvements are leading it into areas where it can do some applications. However no-one is going to rewrite MS Excel or MS Word in WinBatch.
Formatted printing capabilities are weak, but it can control programs like MS Word to format and print a document - but it is not as nice of a process as one could hope for.
The emphasis on WinBatch is a that is is "Utility" language that one would use to write personal and system utility programs rather than full blown applicaitons. So although it is stuffed to the brim with most anything a Utility writer could hope for, people wanting to write Applications, Scientific Analysis Programs, Operating Systems, Web Servers and any extremely large complicatated (as in perhaps tens of thousands of line of code) may find it lacking in advanced capabilites.
However for the target of utilties and small programs, it is the best.
Comments from Other Users:User #1:
In my opinion, Winbatch can't be beat! The majority of PC programming I do involves getting data from my Unisys mainframe, massaging it as necessary, and then spewing it forth to the target. I use other languages, such as Power Basic and Visual Basic, but I keep coming back to Winbatch, for its simple but elegant abilities. I can get data via ODBC or ADO (depending on my whim), bolt directly into Excel via COM, then email the thing directly to the user via Postie.
Winbatch may be called a "utility" language, but for me its a full blown programming language!
Just my 2 cents ...
User #2: The beautiful thing about WinBatch is that programming dummies such as myself can quickly and easily create simple solutions for the little things that come up during the course of our work. That you can come out here and get ideas, info and even scripts that do cool things that you can massage to do what you want makes it an indispensible tool. It's amazing how you can throw a quick utility together and have people say "Cool, dude, you're a freakin' genius" when WinBatch did most of the work for you.