From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Antipov Newsgroups: gmane.emacs.devel Subject: Re: One more string functions change Date: Sat, 28 Jun 2014 20:32:44 +0400 Message-ID: <53AEEE2C.8040705@yandex.ru> References: <53AD8D59.5000207@yandex.ru> <6cf80ae5-a4ad-4839-adfd-14bf973f056f@default> <53AE3B17.4030100@yandex.ru> <3c8f874e-73d7-435e-8898-2085cb76faba@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1403973195 1663 80.91.229.3 (28 Jun 2014 16:33:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Jun 2014 16:33:15 +0000 (UTC) Cc: Emacs development discussions To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 28 18:33:08 2014 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 1X0vYq-0005b6-AW for ged-emacs-devel@m.gmane.org; Sat, 28 Jun 2014 18:33:08 +0200 Original-Received: from localhost ([::1]:55285 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0vYp-0007F2-Rc for ged-emacs-devel@m.gmane.org; Sat, 28 Jun 2014 12:33:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0vYg-0007Eu-Su for emacs-devel@gnu.org; Sat, 28 Jun 2014 12:33:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X0vYZ-0001ow-RV for emacs-devel@gnu.org; Sat, 28 Jun 2014 12:32:58 -0400 Original-Received: from forward9l.mail.yandex.net ([84.201.143.142]:34972) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0vYZ-0001oq-LH for emacs-devel@gnu.org; Sat, 28 Jun 2014 12:32:51 -0400 Original-Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward9l.mail.yandex.net (Yandex) with ESMTP id 1AFA7E61436; Sat, 28 Jun 2014 20:32:49 +0400 (MSK) Original-Received: from smtp1h.mail.yandex.net (localhost [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id A789D13403DB; Sat, 28 Jun 2014 20:32:48 +0400 (MSK) Original-Received: from 146.gprs.mts.ru (146.gprs.mts.ru [213.87.138.146]) by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 2ODdrpw2Gn-WlIaaONj; Sat, 28 Jun 2014 20:32:47 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 0550fa06-5c7e-46c1-b93c-250f011583fb DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1403973168; bh=9RoJbmUudbP6NZ+EO1a0AtIy4u4mAsbTQ8eCx6TmB6M=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=uV5EGbrDZdINL3QWsz3Xd8KiiKhWMEUI+WGte4HGLMj8xccgSGwdoVYO+yZRRR9mB 3wTnHMWl4qP3gpjWx3r2gUAShTxPQNuuYfSqGyFg/tPkeUfHxbglCyb+5g5TYphWSA rfqwzZZUv7MuR1haEaANJ29QfYGt17Nmqhjz9rPA= Authentication-Results: smtp1h.mail.yandex.net; dkim=pass header.i=@yandex.ru User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: <3c8f874e-73d7-435e-8898-2085cb76faba@default> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 84.201.143.142 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:172801 Archived-At: On 06/28/2014 05:48 PM, Drew Adams wrote: >> Value of case-fold-search doesn't affect string-lessp and string-equal. > > Oh, right. What was the reason for that? Anyone know? Someone was too lazy or just didn't consider this important enough - who knows? >>> or: (string-lessp (upper s1) (upper s2)) > > To me, that cliche seems just as easy & clear as (string-lessp s1 s2 t). Sure, but if we treat strings as immutable objects, both 'upper' should create copies; the latter can avoid memory allocation at all and so disprove the well-known "LISP programmers know the value of everything and the cost of nothing" principle. Dmitry