all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs
Date: Tue, 10 Jun 2003 23:33:26 +0100	[thread overview]
Message-ID: <rzqu1axbm15.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: E19OaqQ-0005kS-1I@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

>     > 	[__hpux]: Include sys/_mbstate_t.h.
>
>     Using a macro like __hpux should be done only as a last resort.
>     I hope there is a better way.
>
> One idea is to test using Autoconf for the existence of such a file
> and include it if it exists.

That's the proposal.

> That will work provided there is no case
> where that file exists but including it is harmful.

The question is really whether there is any reason to think it might
be harmful, i.e. why wasn't it done like that originally?  If no-one
knows, it seems best just to do it, as it seems unlikely to cause
grief.

>     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?

Gcc actually defines them.

>     In any case, we try hard not to use system-dependent macros like that
>     and prefer to use the results of configure-time tests.
>
> That is preferable, but with a system as different from GNU as Windows is,
> code for a specific system will tend to be needed often.

This should be just a matter of defining the relevant macros in or via
config.nt.  Similarly with MacOS.

  parent reply	other threads:[~2003-06-10 22:33 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         ` [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   ` Dave Love [this message]
2003-06-12 14:06     ` [Jim Meyering] Re: [Bug-gnulib] strftime merge from Emacs 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

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

  git send-email \
    --in-reply-to=rzqu1axbm15.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.