all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: master 0883e98 1/3: New functions for getting and setting image properties
Date: Sun, 21 Feb 2016 12:55:38 +0100	[thread overview]
Message-ID: <87twl2i8g5.fsf@web.de> (raw)
In-Reply-To: 87ziuuiyo5.fsf@gnus.org

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > AFAIK places stuff is implemented in gv.el now, and that doesn't depend
> > on cl-lib, I think.
>
> Ah, I see.  gv doesn't seem to be loaded by loadup, either, though, so
> is that something that can be used in dumped files?

After reading the sources, AFAIK it's sufficient to load it when
compiling.

You can use the `gv-setter' declare spec in your defun.  Then the byte
compiler will autoload gv and put something like

  (put 'function 'gv-expander [byte code])

in the compiled file.  That doesn't depend on gv when loading.

OTOH when compiling, `setf' forms are expanded to something that doesn't
depend on gv either.

That's just how I think it works, but that stuff is used widely in the
sources.


Michael.




  reply	other threads:[~2016-02-21 11:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160220070344.25183.28197@vcs.savannah.gnu.org>
     [not found] ` <E1aX1a8-0006a1-FW@vcs.savannah.gnu.org>
2016-02-20  7:28   ` master 0883e98 1/3: New functions for getting and setting image properties Lars Ingebrigtsen
2016-02-20 17:00     ` Michael Heerdegen
2016-02-21  2:29       ` Lars Ingebrigtsen
2016-02-21 11:55         ` Michael Heerdegen [this message]
2016-02-22  1:40           ` Lars Ingebrigtsen
2016-02-22 13:15             ` Michael Heerdegen
2016-02-22 16:37               ` Michael Heerdegen
2016-02-23  1:26                 ` Lars Ingebrigtsen

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=87twl2i8g5.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.org \
    /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.