From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs
Date: Sat, 07 Jun 2003 18:50:21 +0300 [thread overview]
Message-ID: <9628-Sat07Jun2003185020+0300-eliz@elta.co.il> (raw)
In-Reply-To: <85n0gtoqk2.fsf@pi.meyering.net> (message from Jim Meyering on Sat, 07 Jun 2003 17:28:13 +0200)
> From: Jim Meyering <jim@meyering.net>
> Date: Sat, 07 Jun 2003 17:28:13 +0200
>
> > I haven't seen WINDOWSNT used before.
> > Here are some of the window-related macros I have seen:
> >
> > _WIN32 WIN32 __WIN32__ __MSDOS__ WINDOWS32
> >
> > WINDOWSNT is what Emacs uses. It is a GNU convention that we do not
> > use the abbreviation "WIN" to refer to Windows. Are those names
> > used in any GNU packages?
>
> Yes. I found those uses in gnulib and the coreutils.
> BTW, is WINDOWSNT an appropriate name for such a macro?
> I've heard that some of the modules using those macros may be
> compiled on non-Windows/NT systems.
I believe WINDOWS32 is a better name. IIRC, GNU Make uses it.
(WINDOWSNT is something that emerged in Emacs historically; it might
not make much sense elsewehere.)
next prev parent reply other threads:[~2003-06-07 15:50 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 ` Eli Zaretskii [this message]
2003-06-07 17:03 ` [Jim Meyering] Re: [Bug-gnulib] " 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 ` [Zlib-devel] Avoiding WIN* macros in GNU code Cosmin Truta
2003-06-13 10:03 ` 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=9628-Sat07Jun2003185020+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--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).