unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: debug declaration.
Date: Thu, 31 Mar 2005 13:21:35 -0500	[thread overview]
Message-ID: <E1DH4IR-00049C-OM@fencepost.gnu.org> (raw)
In-Reply-To: <87zmwlsgat.fsf@xs4all.nl> (message from Lute Kamstra on Wed, 30 Mar 2005 10:12:42 +0200)

    > OTOH it's closer to what I meant by "turn it into a macro" (in the
    > comment that prompted you to look into this whole thing).  Ideally
    > define-generic-mode should (just like define-derived-mode does)
    > generate stand-alone code which does not require generic.el.

    I considered this when I started to work on generic.el, but moving all
    the code into define-generic-mode would lead to some code duplication.
    Especially generic-mode-set-comments is a bit long.

I see nothing wrong with having it load generic.el.
That file is short.  I think no further change is called for,
and it would be better to spend the time on something else.

    Maybe it's a good thing if define-generic-mode evaluated all it's
    arguments during macro expansion.

Macros should never evaluate their arguments during macro expansion.
They should always substitute them into the expansion so they will
be evaluated when the expansion is *run*.

      reply	other threads:[~2005-03-31 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 15:54 debug declaration Lute Kamstra
2005-03-23 18:18 ` Stefan Monnier
2005-03-25 11:06   ` Lute Kamstra
2005-03-25 15:14     ` Stefan Monnier
2005-03-27  3:52       ` Richard Stallman
2005-03-30  8:12       ` Lute Kamstra
2005-03-31 18:21         ` Richard Stallman [this message]

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=E1DH4IR-00049C-OM@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).