From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: composition bug Date: Thu, 18 Sep 2008 02:08:02 -0400 Message-ID: References: <87hc8rn3ws.fsf@cyd.mit.edu> <87r67u3k52.fsf@elegiac.orebokech.com> <87iqt53mk7.fsf@elegiac.orebokech.com> <87zlmcxsq1.fsf@elegiac.orebokech.com> <87zlm86191.fsf@elegiac.orebokech.com> <87prn457u2.fsf@elegiac.orebokech.com> <873ajy603u.fsf@elegiac.orebokech.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1221718100 7172 80.91.229.12 (18 Sep 2008 06:08:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Sep 2008 06:08:20 +0000 (UTC) Cc: cyd@stupidchicken.com, Romain Francoise , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 18 08:09:16 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KgChX-0000Eu-F4 for ged-emacs-devel@m.gmane.org; Thu, 18 Sep 2008 08:09:16 +0200 Original-Received: from localhost ([127.0.0.1]:46325 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KgCgV-0006dL-Ml for ged-emacs-devel@m.gmane.org; Thu, 18 Sep 2008 02:08:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KgCgQ-0006bu-E5 for emacs-devel@gnu.org; Thu, 18 Sep 2008 02:08:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KgCgO-0006be-Iu for emacs-devel@gnu.org; Thu, 18 Sep 2008 02:08:05 -0400 Original-Received: from [199.232.76.173] (port=46924 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KgCgO-0006bb-GA for emacs-devel@gnu.org; Thu, 18 Sep 2008 02:08:04 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:38287 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KgCgO-0006ac-MM for emacs-devel@gnu.org; Thu, 18 Sep 2008 02:08:04 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiQFAOOM0UhMCrQ4/2dsb2JhbACBZLApCIZ0YAMIfIED X-IronPort-AV: E=Sophos;i="4.32,419,1217822400"; d="scan'208";a="27024733" Original-Received: from 76-10-180-56.dsl.teksavvy.com (HELO ceviche.home) ([76.10.180.56]) by ironport2-out.teksavvy.com with ESMTP; 18 Sep 2008 02:08:02 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id A7694B40B1; Thu, 18 Sep 2008 02:08:02 -0400 (EDT) In-Reply-To: (Kenichi Handa's message of "Thu, 18 Sep 2008 10:23:23 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:103930 Archived-At: > I'm always confused by int and EMACS_INT. "struct it" and > "struct text_pos" in dispextern.h uses "int" for > buffer/string positions, and xdisp.c calls functions in > composite.c with those values. So, there exist mixture of > int and EMACS_INT. Shouldn't all of them use EMACS_INT for > positions (and perhaps for string length)? Yes. It's important for buffers (or strings) larger than 2GB. We probably don't need to worry about strings larger than 2GB for a few more years, but for buffers it's worthwhile to take it into account. Stefan