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: issues with recent doprnt-related changes Date: Fri, 06 May 2011 14:13:06 -0300 Message-ID: References: <4DB50AB9.6060100@cs.ucla.edu> <83tydmaeo3.fsf@gnu.org> <4DB65FF1.5010003@cs.ucla.edu> <83aafb8p4a.fsf@gnu.org> <4DB8ABEA.3080503@cs.ucla.edu> <4DB9146D.2040702@cs.ucla.edu> <4DB9E5FF.9020506@cs.ucla.edu> <83d3k571ee.fsf@gnu.org> <4DC10012.8020809@cs.ucla.edu> <4DC1692B.1090101@cs.ucla.edu> <83ei4cnau6.fsf@gnu.org> <83vcxnlvl9.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1304702010 5603 80.91.229.12 (6 May 2011 17:13:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 6 May 2011 17:13:30 +0000 (UTC) Cc: 8545@debbugs.gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 06 19:13:19 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QIOaZ-00069M-OW for ged-emacs-devel@m.gmane.org; Fri, 06 May 2011 19:13:15 +0200 Original-Received: from localhost ([::1]:48631 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QIOaY-00046i-QU for ged-emacs-devel@m.gmane.org; Fri, 06 May 2011 13:13:14 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:34525) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QIOaW-00046b-OB for emacs-devel@gnu.org; Fri, 06 May 2011 13:13:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QIOaV-0000jG-UY for emacs-devel@gnu.org; Fri, 06 May 2011 13:13:12 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:33390) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QIOaV-0000jC-Rg for emacs-devel@gnu.org; Fri, 06 May 2011 13:13:11 -0400 Original-Received: from 121-249-126-200.fibertel.com.ar ([200.126.249.121]:46305 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QIOaU-0004Up-K8; Fri, 06 May 2011 13:13:11 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 72F4B66248; Fri, 6 May 2011 14:13:06 -0300 (ART) In-Reply-To: <83vcxnlvl9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 May 2011 18:03:46 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.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:139182 Archived-At: >> And we never show "length, including >> terminating nul-byte" to Elisp, so the nul-byte shouldn't matter > If you are sure of that, then I agree it's fine to use > MOST_POSITIVE_FIXNUM+1. I wasn't sure. I do see in C variables that > explicitly use the string position of the null byte; I was afraid that > they could somehow leak to Lisp. I don't know enough to guarantee you that they can never leak to Lisp, but I can't think of any reason why they should. And note that "the position of the nul byte" is the same as "the length of the list", so it's still <= MOST_POSITIVE_FIXNUM. It's only the position after the nul byte that would overflow. Stefan