From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze on October 1 Date: Thu, 27 Sep 2012 18:10:29 +0900 Message-ID: <878vbval16.fsf@gnu.org> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348737058 23863 80.91.229.3 (27 Sep 2012 09:10:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Sep 2012 09:10:58 +0000 (UTC) Cc: eliz@gnu.org, cyd@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 27 11:11:03 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1THA7b-0004qP-3D for ged-emacs-devel@m.gmane.org; Thu, 27 Sep 2012 11:11:03 +0200 Original-Received: from localhost ([::1]:38124 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THA7V-00011p-SO for ged-emacs-devel@m.gmane.org; Thu, 27 Sep 2012 05:10:57 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:54862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THA7T-00011e-Vj for emacs-devel@gnu.org; Thu, 27 Sep 2012 05:10:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1THA7S-0006Tc-Kj for emacs-devel@gnu.org; Thu, 27 Sep 2012 05:10:55 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:52569) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THA7S-0006TW-HH for emacs-devel@gnu.org; Thu, 27 Sep 2012 05:10:54 -0400 Original-Received: from 253.240.accsnet.ne.jp ([202.220.240.253]:58965 helo=mongkok) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1THA7R-0001zu-B9; Thu, 27 Sep 2012 05:10:53 -0400 In-Reply-To: (message from Stefan Monnier on Wed, 26 Sep 2012 15:47:39 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 208.118.235.10 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153624 Archived-At: In article , Stefan Monnier 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 handa@gnu.org