From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.eieio,gmane.emacs.devel Subject: Re: Cleaning up the EIEIO namespace Date: Mon, 18 Feb 2013 22:32:06 +0100 Message-ID: <87a9r18g15.fsf@engster.org> References: <87sj51fakd.fsf@engster.org> <87k3qcfa4x.fsf@engster.org> <511C39A9.4000403@siege-engine.com> <874nhefvcr.fsf@engster.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1361223142 32260 80.91.229.3 (18 Feb 2013 21:32:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Feb 2013 21:32:22 +0000 (UTC) Cc: emacs-devel@gnu.org, cedet-eieio@lists.sourceforge.net, "Eric M. Ludlam" To: Stefan Monnier Original-X-From: cedet-eieio-bounces@lists.sourceforge.net Mon Feb 18 22:32:42 2013 Return-path: Envelope-to: sf-cedet-eieio@m.gmane.org Original-Received: from lists.sourceforge.net ([216.34.181.88]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U7YKG-0005ia-28 for sf-cedet-eieio@m.gmane.org; Mon, 18 Feb 2013 22:32:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=sfs-ml-4.v29.ch3.sourceforge.com) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1U7YJv-0001U9-5F; Mon, 18 Feb 2013 21:32:19 +0000 Original-Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1U7YJt-0001Ts-VJ for cedet-eieio@lists.sourceforge.net; Mon, 18 Feb 2013 21:32:17 +0000 X-ACL-Warn: Original-Received: from randomsample.de ([83.169.19.17]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1U7YJr-0006EV-6L for cedet-eieio@lists.sourceforge.net; Mon, 18 Feb 2013 21:32:17 +0000 Original-Received: from dslc-082-083-033-249.pools.arcor-ip.net ([82.83.33.249] helo=spaten) by randomsample.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1U7YJj-0004A7-3F; Mon, 18 Feb 2013 22:32:07 +0100 In-Reply-To: (Stefan Monnier's message of "Thu, 14 Feb 2013 17:16:21 -0500") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2.93 (gnu/linux) Mail-Followup-To: Stefan Monnier , "Eric M. Ludlam" , cedet-eieio@lists.sourceforge.net, emacs-devel@gnu.org X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1U7YJr-0006EV-6L X-BeenThere: cedet-eieio@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cedet-eieio-bounces@lists.sourceforge.net Xref: news.gmane.org gmane.emacs.eieio:148 gmane.emacs.devel:157144 Archived-At: Stefan Monnier writes: >>> Actually, there's a misunderstanding here: >>> - setf was indeed part of CL, but being a macro it was accepted >>> (i.e. you don't need to have it defined at run-time, since it's > >>> macro-expanded during compilation). >>> - setf is part of core Elisp in Emacs-24.3. >>> So maybe we don't need oref/oset at all. >> Yes, although I like "(oset foo bar 'baz)" much better than the verbose >> (setf (cl-slot-value foo 'bar) 'baz) >> But I can understand that you want to get rid of it, and package writers >> can still define their own macros/accessors. > > I actually don't particular care if we keep them or not, except that if > we keep them, we need to give them a prefix. OK. I guess we'd have to use eieio-oref/oset then, since those functions are not from CLOS (given that 'cl' means that thing I thought it means, but I might just be confused :) ). >> Our problem on the CEDET side is that we want to stay compatible with >> older Emacsen, so we'll need some compat package. > > We can either introduce an eieio-compat package full of defaliases, or > do what we did with cl/cl-lib and turn eieio.el into a deprecated compat > package (and introduce a new package eieio-lib to replace it). I meant a compat package in CEDET upstream, so that it can run on older Emacsen if we stop shipping our own EIEIO version. As long as we're obsolete-aliasing the old names, I don't see why we would need a compat package in Emacs? -David ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/