LuaBinaries Why so many Win32 bindings

["Jeff Wise" <jwise@...>]

When this sort of problem is encountered on the mainframe, there are two
common approaches:

1. Distribute object code which is linked on install instead of executables.
The install process fixes the problem.

2. In the routine, put a compile-time switch which calls an assembler
language interface to acquire/return the storage (or whatever library
function is generating the problem). This is not very portable in the usual
sense, but since this compile-time switch can call a unique routine for each
relevant distribution, it accomplishes the given task of being independent
of the vagaries of each compiler DLL.

Perhaps these solutions are not appropriate, but I'm not knowledgeable
enough of Windoze to tell.