From: Paul Eggert <eggert@cs.ucla.edu>
To: Chong Yidong <cyd@gnu.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>, 12215@debbugs.gnu.org
Subject: bug#12215: CSET is unnecessarily confusing
Date: Thu, 23 Aug 2012 20:57:48 -0700 [thread overview]
Message-ID: <5036FBBC.2000108@cs.ucla.edu> (raw)
In-Reply-To: <87fw7d3qan.fsf@gnu.org>
On 08/23/2012 08:46 PM, Chong Yidong wrote:
> Maybe we could use macros that are a no-op under CPP, and serve only as
> guides for a non-CPP code transformation tool.
How about if we use a naming convention that the code transformation
tool could pick out? That is, instead of
bset_directory (b, current_buffer ? BVAR (current_buffer, directory) : Qnil);
we have something like this:
b->Directory = current_buffer ? current_buffer->Directory : Qnil;
Here the convention is that the Lisp field names start with
a capital letter. Almost any naming convention will do.
This is straight C, so the preprocessor would not need to be
used until we have a garbage collector that needs it.
next prev parent reply other threads:[~2012-08-24 3:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 0:04 bug#12215: CSET is unnecessarily confusing Paul Eggert
2012-08-17 4:12 ` Dmitry Antipov
2012-08-21 16:55 ` Stefan Monnier
2012-08-22 3:25 ` Paul Eggert
2012-08-22 13:27 ` Stefan Monnier
2012-08-22 16:35 ` Paul Eggert
2012-08-22 16:50 ` Dmitry Antipov
2012-08-23 7:02 ` Paul Eggert
2012-08-23 12:26 ` Stefan Monnier
2012-08-23 14:40 ` Paul Eggert
2012-08-24 3:46 ` Chong Yidong
2012-08-24 3:57 ` Paul Eggert [this message]
2012-08-24 4:26 ` Dmitry Antipov
2012-08-24 15:10 ` Stefan Monnier
2012-08-24 17:19 ` Paul Eggert
2012-08-24 17:27 ` Tom Tromey
2012-08-24 18:11 ` Paul Eggert
2012-08-24 21:12 ` Stefan Monnier
2012-08-25 0:17 ` Paul Eggert
2012-08-25 1:58 ` Stefan Monnier
2012-08-26 5:05 ` Paul Eggert
2012-08-21 17:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5036FBBC.2000108@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=12215@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=dmantipov@yandex.ru \
/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.