From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 11617@debbugs.gnu.org
Subject: bug#11617: Don't use 'register'; these days it's not needed.
Date: Mon, 04 Jun 2012 09:06:42 -0400 [thread overview]
Message-ID: <jwvpq9ftei7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4FCB91E9.1060101@cs.ucla.edu> (Paul Eggert's message of "Sun, 03 Jun 2012 09:33:45 -0700")
>> While `register' has been unnecessary for a while
>> now, I don't see why it would hurt.
> It hurts because it wastes developers' time, and has done so
> for many years.
No it doesn't and hasn't.
> /* If we use `register' here, gcc-4.0.2 on amd64 using
> -DUSE_LISP_UNION_TYPE complains further down that we're getting the
> address of `force'. Go figure. */
Right, compilers have bugs, and we sometimes bump into them. If it's
not with "register" it's with something else.
> This stuff is all bogus and our lives would be a tiny bit simpler
> if it vanished.
In my world, the keyword "register" is just another kind of whitespace.
So just like I don't want to install a patch that "cleans up the
whitespace" I'd rather not install your patch. OTOH, just like for
whitespace, it's perfectly fine for regular patches to remove "register"
in the code they touch.
Stefan
next prev parent reply other threads:[~2012-06-04 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 6:06 bug#11617: Don't use 'register'; these days it's not needed Paul Eggert
2012-06-03 14:24 ` Eli Zaretskii
2012-06-03 14:50 ` Chong Yidong
2012-06-03 15:09 ` Eli Zaretskii
2012-06-03 15:22 ` Stefan Monnier
2012-06-03 16:33 ` Paul Eggert
2012-06-04 13:06 ` Stefan Monnier [this message]
2012-06-04 14:40 ` Paul Eggert
2012-06-04 19:30 ` Stefan Monnier
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=jwvpq9ftei7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11617@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).