From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel,gmane.emacs.eieio Subject: Re: Cleaning up the EIEIO namespace Date: Tue, 12 Feb 2013 23:10:10 +0100 Message-ID: <87sj51fakd.fsf@engster.org> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1360707035 4082 80.91.229.3 (12 Feb 2013 22:10:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Feb 2013 22:10:35 +0000 (UTC) Cc: "Eric M. Ludlam" , cedet-eieio@lists.sourceforge.net, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 12 23:10:54 2013 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 1U5O3w-0008WT-4n for ged-emacs-devel@m.gmane.org; Tue, 12 Feb 2013 23:10:52 +0100 Original-Received: from localhost ([::1]:38567 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5O3c-0001q5-OD for ged-emacs-devel@m.gmane.org; Tue, 12 Feb 2013 17:10:32 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:38624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5O3W-0001pt-8U for emacs-devel@gnu.org; Tue, 12 Feb 2013 17:10:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5O3P-0003KF-KX for emacs-devel@gnu.org; Tue, 12 Feb 2013 17:10:26 -0500 Original-Received: from randomsample.de ([83.169.19.17]:52439) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5O3P-0003Gt-7J for emacs-devel@gnu.org; Tue, 12 Feb 2013 17:10:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=xn0hTnn2zxzaspp4MHePcDbC0XGXZ8IgyyEAJXd3xSQ=; b=Hnc3HuvobJ1sAHN4X+VUGLV7yRKGFThyGbWuNYLWYBV5Li2qeVy3amdOWSt62rcUQ2dXcts+dbEowq6gEp7926rnYb4I3QKWYySHKSexFwm241y1YbxCJPJenRDpcPcn; Original-Received: from dslc-082-083-041-227.pools.arcor-ip.net ([82.83.41.227] helo=spaten) by randomsample.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1U5O3G-0007Fv-SW; Tue, 12 Feb 2013 23:10:11 +0100 In-Reply-To: (Stefan Monnier's message of "Sun, 10 Feb 2013 13:10:48 -0500") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2.92 (gnu/linux) Mail-Followup-To: Stefan Monnier , cedet-eieio@lists.sourceforge.net, emacs-devel@gnu.org, "Eric M. Ludlam" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 83.169.19.17 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:156989 gmane.emacs.eieio:130 Archived-At: Stefan Monnier writes: > Here is a patch that attempts to clean up part of the EIEIO namespace. > If you like it, please install it upstream, so it will get merged into > Emacs later on. If you prefer, I can install it into Emacs directly and > you'll merge it later on upstream, of course. Thank you for the patch. I know it cannot have been fun. :-) I didn't have time yet to look at your patch in detail. I did apply it to CEDET trunk and got byte-compile errors because there's eieio-class-parent as well as eieio--class-parent. As for the general direction of the cleanup: We did discuss this a bit in the bug report you opened for it some time ago, and Eric stated that he'd at least like to keep the CLOS-compatible names without having to prefix everything with 'eieio-'. Your suggestion was to use the shorter 'cl-' prefix instead, and at least I think that is a good compromise. So instead of using 'eieio-class-name', for instance, we'd rather use 'cl-class-name'. I don't know enough CLOS to see which other names are affected by this (but I could easily look it up, of course). Regarding the merge procedure: I'm a bit hesitant to merge the current CEDET trunk to Emacs just yet because the Java-support is pretty much in flux right now, so I'd prefer if you just apply it in Emacs trunk. We were planning to move EIEIO development to Emacs trunk anyway. I'm actually hoping that we can remove EIEIO from CEDET upstream some time later this year. -David