From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: No setf-method known for funcall
Date: Thu, 18 Aug 2005 21:59:28 -0400 [thread overview]
Message-ID: <barmar-317B0B.21592818082005@comcast.dca.giganews.com> (raw)
In-Reply-To: 871x4r9vbx.fsf@thalassa.informatimago.com
In article <871x4r9vbx.fsf@thalassa.informatimago.com>,
Pascal Bourguignon <spam@mouse-potato.com> wrote:
> kcin@mytrashmail.com writes:
>
> > I'd like to setf a "place" which is retrieved indirectly with a funcall
> > call:
> >
> >
> > (defstruct my
> > a b)
> >
> > (setq myinstance (make-my))
> >
> > (setf (my-a myinstance) 33) ; this works
> >
> > (setq my-get-func 'my-a)
> > (setf (funcall my-get-func myinstance) 33)
> > ; this doesn't work
> > ; "No setf-method known for funcall"
>
> Write a defsetf-er for funcall!
>
>
> (require 'cl)
>
> (defmacro with-gensyms (syms &rest body)
> `(let ,(mapcar (lambda (s) `(,s ',(gensym (symbol-name s)))) syms) ,@body))
>
> (define-setf-method funcall (fun &rest args)
> "setf-method for (funcall fun args...)"
> (let* ((vfun (eval fun))
This won't work if the code is compiled. SETF is expanded at compile
time, but you need to EVAL the variable at run time (and need to do it
each time through the loop).
> (vexp (get-setf-method `(,vfun ,@args))))
> (message "\n%S\n" vexp)
> (when (null vexp)
> (error "There is no defsetf for %s in %S"
> vfun (cons fun args)))
> vexp))
In real Common Lisp, you can only SETF a FUNCALL if the function
argument is a literal, since SETF can get the function and its SETF
method. E.g. you can do:
(setf (funcall #'car) ...)
but you can't do:
(let ((func #'car))
(setf (funcall func) ...))
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2005-08-19 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 12:31 No setf-method known for funcall kcin
2005-08-18 14:24 ` Pascal Bourguignon
2005-08-19 1:59 ` Barry Margolin [this message]
2005-08-19 3:47 ` Pascal Bourguignon
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=barmar-317B0B.21592818082005@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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.
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).