Post by Mayayana
Years ago I had a friend who was fond of Perl and he
showed me a Perl library that allowed for calling Win32
API. It was interesting, but since I could already do
the real thing there wasn't much point. Script is already
interpreted, but calling something like Win32 API via
commandline would require very clunky wrapping because
all the data types have to be converted in both directions.
If accessing Windows API from the command line, rather than a script, I use
winapiexec. Though, it's not efficient if used many times in a batch file,
or in a loop.
If from a script, they're: Take Command Console LE, AutoHotkey, and AutoIt.
Also a Pascal scripting tool which I "made" using a ready-to-use language
interpreter Delphi library. It already include a Pascal interpreter, so only
a little addition was needed.
I also made some tools to make C#, VB.NET, and JScript.NET scriptable. But
because they need .NET crap, I couldn't bear the program loading overhead.
So I rarely uses it. Python is also unbearable like .NET crap. And Node.js
is the worst one. These tools aren't efficient for small to small-medium
There are also OCXs specifically for accessing Windows API from e.g. WSH,
but IMO, they don't count because it's the OCX which accesses Windows API.