From: Dmitry Antipov <dmantipov@yandex.ru>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: Using 'register' and ^L
Date: Wed, 10 Sep 2014 07:12:09 +0400 [thread overview]
Message-ID: <540FC189.3070309@yandex.ru> (raw)
1) Is there a reason to use explicit 'register' variables nowadays?
This encumbers sources with no measurable benefits; moreover,
some GC tracing/debugging techniques assumes that you can take
an address of any Lisp_Object, which is effectively blocked by
using 'register'.
2) Why still using ^L? It looks like a huge empty space in patches
showing as attachment in some e-mail clients, and I'm curious
whether someone still uses a printing system relying on ^L page
breaks :-).
Dmitry
next reply other threads:[~2014-09-10 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 3:12 Dmitry Antipov [this message]
2014-09-10 4:46 ` Using 'register' and ^L Stephen J. Turnbull
2014-09-10 5:30 ` Paul Eggert
2014-09-10 13:11 ` Stefan Monnier
2014-09-10 17:37 ` Richard Stallman
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=540FC189.3070309@yandex.ru \
--to=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).