Yes, that's all correct. Although Microsoft now simply calls it the
"Windows" API, it used to be called "Win32".
At Thu, 22 Sep 2011 22:34:47 -0700, John Clements wrote:
>
> On Sep 22, 2011, at 10:22 PM, Neil Van Dyke wrote:
>
> > Matthew or someone can give an authoritative answer, but if this
On Sep 22, 2011, at 10:22 PM, Neil Van Dyke wrote:
> Matthew or someone can give an authoritative answer, but if this lets you
> sleep tonight... I suspect the "win32" in Racket is fine, and that Visual
> Studio just has a backward-compatibility awkwardness in naming.
>
> Win32 was the name o
Matthew or someone can give an authoritative answer, but if this lets
you sleep tonight... I suspect the "win32" in Racket is fine, and that
Visual Studio just has a backward-compatibility awkwardness in naming.
Win32 was the name of one of the generations of Windows API, and I
believe that u
In distributing compiled binaries for Windows, I'm trying to cover all of the
bases for the required DLLs. As far as I can tell from Visual Studio 2010,
there are only two flavors, 32-bit and 64-bit. However, I see that on at least
one of my students' machines, the system-library-subpath comes
4 matches
Mail list logo
