From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Subtle error defining VALMASK?
Date: Wed, 10 Sep 2014 09:54:52 -0700 [thread overview]
Message-ID: <5410825C.6070704@cs.ucla.edu> (raw)
In-Reply-To: <54106EA4.9000405@yandex.ru>
Dmitry Antipov wrote:
> fprintf (stderr, "0x%lx 0x%lx\n", VALMASK, VAL_MAX);
That's not a problem with the #define; it's a problem with the enum.
It's simpler to omit the enum, so I did that in trunk bzr 117854.
For portability that format string should be "0x%"pI"x 0x%"pI"x\n".
next prev parent reply other threads:[~2014-09-10 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:57 Subtle error defining VALMASK? Dmitry Antipov
2014-09-10 14:58 ` Paul Eggert
2014-09-10 15:30 ` Dmitry Antipov
2014-09-10 16:54 ` Paul Eggert [this message]
2014-09-10 17:25 ` More issues with r117851 [Was: Re: Subtle error defining VALMASK?] Dmitry Antipov
2014-09-10 20:57 ` Paul Eggert
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=5410825C.6070704@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dmantipov@yandex.ru \
--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).