all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: npostavs@users.sourceforge.net
Cc: 27016@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Rafael D Sorkin <rsorkin@perimeterinstitute.ca>
Subject: bug#27016: possible bug in `defsetf'
Date: Mon, 10 Jul 2017 02:26:14 +0200	[thread overview]
Message-ID: <87fue5i1cp.fsf@drachen> (raw)
In-Reply-To: <871sppgyhb.fsf@users.sourceforge.net> (npostavs's message of "Sun, 09 Jul 2017 16:13:36 -0400")

npostavs@users.sourceforge.net writes:

> Here's a patch for it: [...]

Thanks for working on this.  AFAIU I think it should work.

> @@ -146,12 +149,15 @@ (defmacro gv-define-expander (name handler)
>  HANDLER is a function which takes an argument DO followed by the same
>  arguments as NAME.  DO is a function as defined in `gv-get'."
>    (declare (indent 1) (debug (sexp form)))
> -  ;; Use eval-and-compile so the method can be used in the same file as it
> -  ;; is defined.
> -  ;; FIXME: Just like byte-compile-macro-environment, we should have something
> -  ;; like byte-compile-symbolprop-environment so as to handle these things
> -  ;; cleanly without affecting the running Emacs.
> -  `(eval-and-compile (put ',name 'gv-expander ,handler)))
> +  ;; Push onto `byte-compile-macro-environment' so the method can be
> +  ;; used in the same file as it is defined.
> +  (when (boundp 'byte-compile-macro-environment)
> +    (push (cons :gv-expanders
> +                (cons (cons name handler)
> +                      (cdr (assq :gv-expanders
> +                                 byte-compile-macro-environment))))
> +          byte-compile-macro-environment))
> +  `(put ',name 'gv-expander ,handler))

Is it intended to add an :gv-expanders entry to
byte-compile-macro-environment more than once?


Michael.





  reply	other threads:[~2017-07-10  0:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  6:39 bug#27016: possible bug in `defsetf' Rafael D Sorkin
2017-05-22 12:11 ` npostavs
2017-05-22 20:25 ` Rafael D Sorkin
2017-05-22 21:18   ` npostavs
2017-05-22 23:10     ` Michael Heerdegen
2017-05-22 23:23       ` npostavs
2017-05-23  0:45         ` Michael Heerdegen
2017-05-23  0:51           ` npostavs
2017-05-23  1:18             ` Michael Heerdegen
2017-05-22 22:03 ` Rafael D Sorkin
2017-05-22 23:15   ` npostavs
2017-05-24  4:52 ` Rafael D Sorkin
2017-05-24 22:51   ` Michael Heerdegen
2017-05-25  1:50     ` npostavs
2017-05-25  4:59 ` Rafael D Sorkin
2017-05-25  5:01 ` Rafael D Sorkin
2017-05-25 10:38   ` npostavs
2017-05-25 20:26     ` Michael Heerdegen
2017-05-25 20:42       ` Noam Postavsky
2017-05-25 21:31         ` Michael Heerdegen
2017-05-25 23:03           ` npostavs
2017-05-25 23:40             ` Michael Heerdegen
2017-05-26  3:50 ` Stefan Monnier
2017-05-26 22:51   ` npostavs
2017-05-28 20:45     ` Stefan Monnier
2017-07-02 20:47       ` npostavs
2017-07-03 11:25         ` Michael Heerdegen
2017-07-09 20:13           ` npostavs
2017-07-10  0:26             ` Michael Heerdegen [this message]
2017-07-11  1:45               ` npostavs
2017-07-11 16:21             ` Stefan Monnier
2017-07-12  0:55               ` npostavs
2017-07-12  2:01                 ` Stefan Monnier
2017-07-13  4:46                   ` npostavs
2017-07-13 14:25                     ` Stefan Monnier
2017-07-14  0:39                       ` npostavs
2017-07-14  3:48                         ` Stefan Monnier
2017-07-14  4:32                           ` Stefan Monnier
2017-07-15 14:51                             ` npostavs
2017-07-16  1:03                               ` Stefan Monnier
2017-08-08  1:18                                 ` npostavs
2017-05-26  5:05 ` Rafael D Sorkin

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=87fue5i1cp.fsf@drachen \
    --to=michael_heerdegen@web.de \
    --cc=27016@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=npostavs@users.sourceforge.net \
    --cc=rsorkin@perimeterinstitute.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 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.