Re: [PATCH] Delayed loading of image libraries

[Miles Bader <miles@lsi.nec.co.jp>]

Juanma Barranquero <jmbarranquero@wke.es> writes:
>> Images are (currently) perfectly valid lisp values; if we don't want
>> them to be readable and writable to files, we should make them an opaque
>> type.
>
> Reading and writing a lisp value (whether an image, or any other kind)
> does not need image support.  *Processing* one of such values as an
> image (to display it, ask questions about it, etc.) does need it.  At
> that point, code should've asked whether the image type was available. 
> I'm not sure why you do conflate reading/writing with using-as-an-image
> (even if loading an image-representing lisp value ends up displaying it).

You're misreading what I wrote; the point of mentioning reading/writing
is that an `image' in Emacs lisp is just an ordinary lisp value, which
can be stored to a file (using print or whatever), and read back into a
new session.

Previously, the value returned by `create-image' was a valid image,
which could be displayed, even if saved to a file and read back in a new
emacs session.  After your change for windows, this was not true any
longer.  This was a regression, and my change was intended to fix it.

-Miles
-- 
P.S.  All information contained in the above letter is false,
      for reasons of military security.