From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "John Wiegley" Newsgroups: gmane.emacs.devel Subject: Re: Separating obarray handling from abbrevs Date: Mon, 02 Nov 2015 15:21:34 -0500 Organization: New Artisans LLC Message-ID: References: <87d1vvfa1k.fsf@cumego.com> <87r3k95ppo.fsf@cumego.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1446495889 8207 80.91.229.3 (2 Nov 2015 20:24:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 Nov 2015 20:24:49 +0000 (UTC) Cc: Artur Malabarba , Emacs Developers To: =?utf-8?Q?Przemys=C5=82aw?= Wojnowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 02 21:24:45 2015 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 1ZtLek-00083o-MS for ged-emacs-devel@m.gmane.org; Mon, 02 Nov 2015 21:24:43 +0100 Original-Received: from localhost ([::1]:44118 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZtLek-0002Bw-0n for ged-emacs-devel@m.gmane.org; Mon, 02 Nov 2015 15:24:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZtLee-0002BM-CD for emacs-devel@gnu.org; Mon, 02 Nov 2015 15:24:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZtLea-0001Ho-CR for emacs-devel@gnu.org; Mon, 02 Nov 2015 15:24:36 -0500 Original-Received: from mail-qg0-x229.google.com ([2607:f8b0:400d:c04::229]:32999) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZtLea-0001Hi-87 for emacs-devel@gnu.org; Mon, 02 Nov 2015 15:24:32 -0500 Original-Received: by qgeo38 with SMTP id o38so126816198qge.0 for ; Mon, 02 Nov 2015 12:24:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:in-reply-to:date:organization:message-id :references:user-agent:mail-followup-to:mime-version:content-type :content-transfer-encoding; bh=Z0if1F+7cIDtixd2CYos6Cta3voRgJDudDoYtvhtYQ8=; b=Be11Idn50CKKAgIBoICeqqaEuwnF9cUMn+INBkv741TPXngLffbQtXN0Pv9azyhDOe 8DrjSLzJqNcyyHjKqXbL3JrVVlw7R2eUGsF9vONdyefXnAJaenkLeW1sTcC1sRw/VoCf CDvllXbrGKvklwwXAAF7Kx6pNWPqh8Be/CFub96V46L3ykV+XATKSI8JTkDuCtyAMo9y 9DrlFrBS2cRcfDz4db5/zpb9Zga3vWWc19LCBptltAw7VdJu8uDX9dlA5ZGOWJf/kPCm l4kYMlgadeRQSh+7z/5rgUnaOnL2OAoAFhzBMCSkFdaOoCg8JzpSAvutA7KJZmXOZxf9 yU1g== X-Received: by 10.140.93.1 with SMTP id c1mr31525721qge.59.1446495871904; Mon, 02 Nov 2015 12:24:31 -0800 (PST) Original-Received: from Hermes-2.local ([192.54.222.4]) by smtp.gmail.com with ESMTPSA id r73sm8443143qha.48.2015.11.02.12.24.31 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 02 Nov 2015 12:24:31 -0800 (PST) Original-Received: by Hermes-2.local (Postfix, from userid 501) id 2E31A485DB51; Mon, 2 Nov 2015 15:24:33 -0500 (EST) In-Reply-To: <87r3k95ppo.fsf@cumego.com> (=?utf-8?Q?=22Przemys=C5=82aw?= Wojnowski"'s message of "Sun, 01 Nov 2015 23:17:55 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: =?utf-8?Q?Przemys=C5=82aw?= Wojnowski , Artur Malabarba , Emacs Developers X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c04::229 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:193115 Archived-At: >>>>> Przemys=C5=82aw Wojnowski writes: > This way or another obarray's internals should not be abbrev's > concern. It should just use its API to implement own functionality. This > also ease testing, because both parts can be tested separately. Also > obarray functions could be reused in other places - quick grep shows > that obarray-make would be common. I like these changes, and agree that obarrays should have their own abstraction. John