[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Feature freeze on October 1

From: Kenichi Handa
Subject: Re: Feature freeze on October 1
Date: Thu, 27 Sep 2012 18:10:29 +0900

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

> > Your memory is fine.  The workaround code is in ralloc.c and in
> > maybe_unify_char.  But since we still call maybe_unify_char in
> > decode_char, I don't think we can remove those workarounds yet, can
> > we?

> Are there calls to decode_char which aren't prepared to run Elisp code?

maybe_unify_char doesn't run Elisp code but allocates a Lisp
vector and a Lisp chartable via load_charset.

And I'm not sure that all calls to decode_char are prepared
to buffer/string relocation.

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]