[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnulib] Re: [Zlib-devel] Avoiding WIN* macros in GNU code

From: Cosmin Truta
Subject: [Bug-gnulib] Re: [Zlib-devel] Avoiding WIN* macros in GNU code
Date: Thu, 12 Jun 2003 18:07:13 -0400

On Thu, 12 Jun 2003, Richard Stallman wrote:

>     The abbreviation is not WIN, but it is WIN32.
> Same difference.
>     By the way, what is the problem with using WIN32?
> It includes the word "win", and we don't want to call Microsoft
> Windows a win.

I understand. Should we do the same in zlib?
Is there an official GNU coding standard that states this?

There is still a very peculiar problem with WINDOWSNT: it indicates a
version of MS Windows that is based on an NT kernel, as opposed to a
version based on a Win9x kernel. The official _WINNT symbol indicates
exactly this. Software rely on it when calling Windows NT-specific

The confusion created by WINDOWSNT is similar to one created by a
hypothetical REDHAT_LINUX symbol that would mean "GNU/Linux in general".

So may I suggest something like WINDOWS32 or MSWINDOWS32 instead?
I believe no other windowing system uses WINDOWS or WINDOWS32...

I also wish to point out that the introduction of a yet another new
macro doesn't help. The old ones must still be maintained, because
compilers (including gcc/Win32) preset them, and users rely on them.
Like it or not ... those macros are official, and well-known among
Windows programmers.

(After all, is this "Win32" naming thing one of Microsoft's strategic
moves? :)

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]