unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 27016@debbugs.gnu.org, Rafael D Sorkin <rsorkin@perimeterinstitute.ca>
Subject: bug#27016: possible bug in `defsetf'
Date: Thu, 25 May 2017 19:03:11 -0400	[thread overview]
Message-ID: <87mva05ykw.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87o9ugd3oe.fsf@drachen> (Michael Heerdegen's message of "Thu, 25 May 2017 23:31:13 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Noam Postavsky <npostavs@users.sourceforge.net> writes:
>
>> Hmm, I thought it would cause the 'unless t' to happen in the
>> macroexpansion phase as well, but I was wrong. Apparently 'eval-when'
>> doesn't have this effect, only eval-when-compile or eval-and-compile
>> will do the trick.
>
> That also doesn't work.

Oh, hmm, I only checked by evaluating, I didn't actually try compiling
to a separate file.

> #+begin_src emacs-lisp
> (macroexpand '(defsetf foo bar))
> ==>
> '(lambda
>    (do &rest args)
>    (gv--defsetter 'foo
>                   (lambda
>                     (val &rest args)
>                     `(,'bar ,@args ,val))
>                   do args))
> #+end_src

I don't understand where that quote comes from.  I guess I don't really
understand what's going on here as well as I thought.

> When you compile a file with this content:
>
> #+begin_src emacs-lisp
> (eval-and-compile
>   (unless nil
>     (defsetf foo bar)))
> #+end_src
>
> you get an empty .elc.
>
> Isn't that strange?

Yeah, even stranger...






  reply	other threads:[~2017-05-25 23:03 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 [this message]
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
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

  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=87mva05ykw.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=27016@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --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 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).