From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vitalie Spinu Newsgroups: gmane.emacs.devel,gmane.emacs.eieio Subject: Re: Cleaning up the EIEIO namespace Date: Fri, 29 Mar 2013 11:04:33 +0100 Organization: EUR Message-ID: <87y5d6bjym.fsf@gmail.com> 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 X-Trace: ger.gmane.org 1364551484 17218 80.91.229.3 (29 Mar 2013 10:04:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Mar 2013 10:04:44 +0000 (UTC) Cc: emacs-devel@gnu.org, cedet-eieio@lists.sourceforge.net, "Eric M. Ludlam" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 29 11:05:10 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 1ULWBK-0007Es-MN for ged-emacs-devel@m.gmane.org; Fri, 29 Mar 2013 11:05:10 +0100 Original-Received: from localhost ([::1]:51608 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULWAv-0000w2-R4 for ged-emacs-devel@m.gmane.org; Fri, 29 Mar 2013 06:04:45 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:45722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULWAq-0000vt-By for emacs-devel@gnu.org; Fri, 29 Mar 2013 06:04:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULWAn-0007sP-GZ for emacs-devel@gnu.org; Fri, 29 Mar 2013 06:04:40 -0400 Original-Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:52780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULWAn-0007sC-9L for emacs-devel@gnu.org; Fri, 29 Mar 2013 06:04:37 -0400 Original-Received: by mail-wi0-f176.google.com with SMTP id hm14so4034854wib.15 for ; Fri, 29 Mar 2013 03:04:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:organization:references:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=vYLJbeuOznVy2EfpNyiLfiuQO/qCs06/zfn2VmYZBXg=; b=C9w289mTEAn60AMIMDEhkkZW/Qkh6tv02xv5ldjh5lAeM7+PgUL8F5oO2PTa5XpYjK KwK+iNhuvpAj8MKRXwnHEHNgysboBZqbhnFI8Bp3jT3PInJDdjwkLcjnHnTQVEQoFsW6 BRNJBcCcROa/0JR28Bd0hI7FIG9497eb0lMKGibznbCVojpdy6sFet9015RccXXQi8zJ GqYRtGBsa96Xhdjq9CsIJB107eOjAd6TN9wNi9v5o6QKAbgTxil1602g14Wka0gg9IqO alY1YcyYJ9mg7wm4mFwfVyv2z3JBoiDOCOGKbn6B30fjtpgbWgmHjemM5UepS7frr/St GQog== X-Received: by 10.194.92.65 with SMTP id ck1mr2536064wjb.54.1364551475847; Fri, 29 Mar 2013 03:04:35 -0700 (PDT) Original-Received: from localhost (dhcp-077-249-018-128.chello.nl. [77.249.18.128]) by mx.google.com with ESMTPS id o5sm2983728wix.3.2013.03.29.03.04.34 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 29 Mar 2013 03:04:34 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Thu, 14 Feb 2013 17:16:21 -0500") User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::230 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:158415 gmane.emacs.eieio:154 Archived-At: >> Stefan Monnier >> on Thu, 14 Feb 2013 17:16:21 -0500 wrote: >>> 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. Could please eieio-oref/eieio-oset be avoided? oref/oset are so often used that people will start aliasing them anyways. How about replacing eieio-, the most awkward prefix in existence, with simple "eo-", standing for Emacs Objects? Then eoref/eoset can be used as (almost) namespace clean alternatives. Vitalie