Re: Undumpable object type : buffer

Hey, Olivier, good to hear from you!

>>>>> "Ilya" == Ilya N Golubev <[email protected]> writes:

    Ilya> Also, if some operations may easibly be specified for
    Ilya> strings, and sometimes are needed, but currently are
    Ilya> supported only on buffers, this looks like a bug to me.
    Ilya> Fixing it will make temporary buffers unnecessary.

Strings are not (supposed to be[1]) mutable.  Period, end of story.
Not a bug.

Restrictions on dumpable types are a fact of life.  But there should
be a way to finalize the buffers.  I assume we do a gc before dumping,
so I guess it needs to be done by hand.

Possibly we could fix this generically by having a "temporary buffer"
type, which might not need to be restricted in any way, but would
simply be kept on a weak list rather than a regular list, and thus
would be finalized by a gc.

Does adding "(mapcar #'kill-buffer (buffer-list t))" in The Right
Place help?


Footnotes: 
[1]  Yeah, OK, aset works.  But it shouldn't. :-)

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.