From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: compat unification Date: Tue, 16 Nov 2010 10:31:40 -0500 Message-ID: References: <87k4kebiox.fsf@lifelogs.com> <87hbfimpp1.fsf@ginnungagap.bsc.es> <87fwv2bf7h.fsf@lifelogs.com> <87aalaz6ey.fsf@stupidchicken.com> <87y68ujkjl.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1289921515 15780 80.91.229.12 (16 Nov 2010 15:31:55 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 16 Nov 2010 15:31:55 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 16 16:31:50 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PINVe-0004pF-Hb for ged-emacs-devel@m.gmane.org; Tue, 16 Nov 2010 16:31:50 +0100 Original-Received: from localhost ([127.0.0.1]:43045 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PINVd-0008Eq-Sv for ged-emacs-devel@m.gmane.org; Tue, 16 Nov 2010 10:31:49 -0500 Original-Received: from [140.186.70.92] (port=50158 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PINVX-0008Bl-EV for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:31:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PINVW-0005Z5-GL for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:31:43 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:64986 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PINVW-0005Yn-92 for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:31:42 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAKAEcy4kxFpY76/2dsb2JhbACUX40Ee3K/WIVLBIRajWA X-IronPort-AV: E=Sophos;i="4.59,206,1288584000"; d="scan'208";a="82673677" Original-Received: from 69-165-142-250.dsl.teksavvy.com (HELO pastel.home) ([69.165.142.250]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 16 Nov 2010 10:31:41 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id D223BA82A9; Tue, 16 Nov 2010 10:31:40 -0500 (EST) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Tue, 16 Nov 2010 15:10:52 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:132726 Archived-At: > What if... there was an ems-compat function in bzr Emacs. It would be > a, sort of, "official" current-Emacs-to-everything compat layer. It couldn't be part of Emacs: Emacs-22's ems-compat wouldn't be able to come with Emacs-24's compatibility functions, would it? So it'd have to be an ELPA package. You can go some way with such a package, but it has significant limits. E.g. you'll still often want to know whether a feature is supported or not before using it, because you'll want to use some other code if it's not. Also such compatibility definitions may confuse other packages who'd check (fboundp 'foo) to see if a particular feature is present. Stefan