From: Rafael D Sorkin <rsorkin@perimeterinstitute.ca>
To: npostavs@users.sourceforge.net
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
27016@debbugs.gnu.org,
Rafael D Sorkin <rsorkin@perimeterinstitute.ca>
Subject: bug#27016: possible bug in `defsetf'
Date: Wed, 24 May 2017 00:52:34 -0400 [thread overview]
Message-ID: <E1dDOHi-0000sh-3R@mars.pi.local> (raw)
In-Reply-To: your message of Mon, 22 May 2017 19:15:57 -0400
> `defun' takes effect at runtime (or rather it expands to
> `defalias' which operates at runtime), whereas `defsetf' has
> to affect subsequent compilation, so waiting until runtime to
> decide whether the condition is true could not really work.
Well the way I was using it, everything used to work fine. I
found the bug when it stopped working and I was unable to figure
out why.
I had a defsetf inside a conditional in a file that was to be
loaded and/or compiled and then loaded. (Compilation isn't
really the issue.) Before loading that file I set a "switch"
which the conditional referred to. That way a defsetf done
before loading the file could be either overridden or not, as
desired.
I found the ability to control the defsetf this way to be
useful. However, as I wrote before, I only used this device a
few times, not so many that I couldn't adapt to losing it.
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Rafael Sorkin
Perimeter Institute for Theoretical Physics
31 Caroline Street North
Waterloo, ON N2L 2Y5
Canada
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
next prev parent reply other threads:[~2017-05-24 4:52 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 [this message]
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
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=E1dDOHi-0000sh-3R@mars.pi.local \
--to=rsorkin@perimeterinstitute.ca \
--cc=27016@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
/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).