all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: master 5141234acf: Refactor the webp cache code to allow usage by gif_load, too
Date: Mon, 11 Apr 2022 16:29:33 +0300	[thread overview]
Message-ID: <83mtgr694y.fsf@gnu.org> (raw)
In-Reply-To: <875ynf21n0.fsf@yahoo.com> (message from Po Lu on Mon, 11 Apr 2022 21:25:07 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org,  larsi@gnus.org
> Date: Mon, 11 Apr 2022 21:25:07 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Po Lu <luangruo@yahoo.com>
> >> Cc: Lars Ingebrigtsen <larsi@gnus.org>
> >> Date: Mon, 11 Apr 2022 20:15:12 +0800
> >> 
> >> > +  cache->spec = spec;
> >> 
> >> I think this should be marked, since I don't see what protects the spec
> >> from garbage collection otherwise.
> >
> > 'spec' here is img->spec, right?
> 
> Right, but the animation cache can persist after img is gone, right?

It can?  Then how does this work:

      struct anim_cache* cache = anim_get_animation_cache (img->spec);

We pass img->spec to look it up in the cache, don't we?  And we use EQ
to look it up, right?



  reply	other threads:[~2022-04-11 13:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164967696186.12152.11548736665906939483@vcs2.savannah.gnu.org>
     [not found] ` <20220411113602.7A114C0581E@vcs2.savannah.gnu.org>
2022-04-11 12:15   ` master 5141234acf: Refactor the webp cache code to allow usage by gif_load, too Po Lu
2022-04-11 12:44     ` Lars Ingebrigtsen
2022-04-11 12:56       ` Po Lu
2022-04-11 13:04         ` Lars Ingebrigtsen
2022-04-11 13:12           ` Po Lu
2022-04-11 13:15             ` Lars Ingebrigtsen
2022-04-11 13:29               ` Po Lu
2022-04-11 13:58           ` Stefan Monnier
2022-04-11 14:55             ` Lars Ingebrigtsen
2022-04-11 13:12     ` Eli Zaretskii
2022-04-11 13:14       ` Lars Ingebrigtsen
2022-04-11 13:22         ` Eli Zaretskii
2022-04-11 13:25       ` Po Lu
2022-04-11 13:29         ` Eli Zaretskii [this message]
2022-04-11 13:32           ` Po Lu
2022-04-11 14:55       ` 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=83mtgr694y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    /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.