From: "Drew Adams" <drew.adams@oracle.com>
To: 13343@debbugs.gnu.org
Subject: bug#13343: 24.3.50; give examples using `gv-define-expander' and `gv-letplace'
Date: Wed, 2 Jan 2013 15:52:35 -0800 [thread overview]
Message-ID: <AC9A8DEABD534C5D941BADBE89446CE0@us.oracle.com> (raw)
(elisp) `Adding Generalized Variables' says only this:
For more control over the expansion, see the macro `gv-define-expander'.
The macro `gv-letplace' can be useful in defining macros that perform
similarly to `setf'; for example, the `incf' macro of Common Lisp.
Consult the source file `gv.el' for more details.
That's a complete cop-out. Give at least one example of using each of
`gv-define-expander' and `gv-letplace'.
Telling users to refer to gv.el for information about using these macros
is off-base. Neither the commentary in that file nor the doc strings of
these two macros help.
We should not send users off to analyze the _implementation_ of these
macros in order to figure out how to use them to define generalized
variables. We should describe what these macros do specifically, and
show how to use them.
All the current doc says, to describe these macros, is (a)
`gv-define-expander' gives you "more control" and (b) `gv-letplace' "can
be useful".
"See the macro", indeed. See what? It's implementation? Emacs users
deserve better.
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2012-12-31 on ODIEONE
Bzr revision: 111388 rudalics@gmx.at-20121231113513-subz2dazg6yjukzh
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-IC:/Devel/emacs/build/include --ldflags -LC:/Devel/emacs/build/lib'
next reply other threads:[~2013-01-02 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 23:52 Drew Adams [this message]
2019-08-16 6:58 ` bug#13343: 24.3.50; give examples using `gv-define-expander' and `gv-letplace' Lars Ingebrigtsen
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=AC9A8DEABD534C5D941BADBE89446CE0@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13343@debbugs.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.