unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cosmin Truta <cosmin@cs.toronto.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Zlib-devel] Avoiding WIN* macros in GNU code
Date: Thu, 12 Jun 2003 18:07:13 -0400	[thread overview]
Message-ID: <Pine.GSO.4.44.0306121736180.11754-100000@qew.cs> (raw)
In-Reply-To: <E19QZ6R-0007Wo-AB@fencepost.gnu.org>


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
services.

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,
Cosmin

  reply	other threads:[~2003-06-12 22:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 10:32 [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs Dave Love
2003-06-06 13:24 ` Jason Rumney
2003-06-09 22:53   ` [Jim Meyering] " Andrew Innes
2003-06-10 22:36     ` Dave Love
2003-06-10 22:34   ` Dave Love
2003-06-10 22:51     ` [Jim Meyering] Re: [Bug-gnulib] " Jason Rumney
2003-06-11 10:14       ` Bruno Haible
2003-06-11 10:29         ` Jason Rumney
2003-06-11 17:29           ` [Jim Meyering] " Paul Eggert
2003-06-11 18:38             ` Eli Zaretskii
2003-06-11 18:52               ` [Jim Meyering] Re: [Bug-gnulib] " Paul Eggert
2003-06-11 19:26             ` Bruno Haible
2003-06-12 22:42       ` [Jim Meyering] " Dave Love
2003-06-13 14:53         ` Paul Eggert
2003-06-16 22:15           ` [Jim Meyering] Re: [Bug-gnulib] " Dave Love
2003-06-17  4:15             ` Paul Eggert
2003-06-17 11:10               ` Stephen J. Turnbull
2003-06-07 10:22 ` [Jim Meyering] " Richard Stallman
2003-06-07 15:28   ` Jim Meyering
2003-06-07 15:50     ` [Jim Meyering] Re: [Bug-gnulib] " Eli Zaretskii
2003-06-07 17:03       ` Bruno Haible
2003-06-07 18:46         ` [Jim Meyering] " Eli Zaretskii
2003-06-09  0:21         ` [Jim Meyering] Re: [Bug-gnulib] " Richard Stallman
2003-06-09 21:10   ` Avoiding WIN* macros in GNU code [was Re: [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs] Derek Robert Price
2003-06-12  5:52     ` [Zlib-devel] " Cosmin Truta
2003-06-12  6:31       ` Miles Bader
2003-06-12 20:55       ` Richard Stallman
2003-06-12 22:07         ` Cosmin Truta [this message]
2003-06-13 10:03           ` [Zlib-devel] Avoiding WIN* macros in GNU code Jason Rumney
2003-06-15 15:59           ` Richard Stallman
2003-06-10 22:33   ` [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs Dave Love
2003-06-12 14:06     ` Richard Stallman
2003-06-12 16:11       ` [Jim Meyering] " Benjamin Riefenstahl
2003-06-12 17:59       ` Jason Rumney
2003-06-12 18:43         ` Eli Zaretskii
2003-06-13 22:03         ` Richard Stallman
2003-06-16 21:55       ` Dave Love

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.44.0306121736180.11754-100000@qew.cs \
    --to=cosmin@cs.toronto.edu \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).