From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric M. Ludlam" Newsgroups: gmane.emacs.devel Subject: Re: A unified project root interface Date: Thu, 21 Mar 2013 00:07:13 -0400 Message-ID: <514A8771.6080900@siege-engine.com> References: <20130309174419.6e1cadb4@forcix.kollektiv-hamburg.de> <513FBA1C.5040100@siege-engine.com> <87vc8vyy66.fsf@engster.org> <5143C11D.8070705@siege-engine.com> <87sj3vv35h.fsf@engster.org> <20130316160203.6b889aba@forcix.kollektiv-hamburg.de> <87ehffuf1g.fsf@engster.org> <20130317001630.125e1987@forcix.kollektiv-hamburg.de> <87y5dmsz5u.fsf@engster.org> <20130317191817.764a44f5@forcix.kollektiv-hamburg.de> <87ppywtj9s.fsf@engster.org> <87li9juabi.fsf@engster.org> <87d2uvtdeb.fsf@engster.org> <874ng6tugb.fsf@engster.org> <87ppyurpxa.fsf@engster.org> <514A5A68.3070907@siege-engine.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1363838844 13464 80.91.229.3 (21 Mar 2013 04:07:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Mar 2013 04:07:24 +0000 (UTC) Cc: Jorgen Schaefer , John Yates , David Engster , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 21 05:07:45 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 1UIWn2-0005Rk-9d for ged-emacs-devel@m.gmane.org; Thu, 21 Mar 2013 05:07:44 +0100 Original-Received: from localhost ([::1]:48418 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIWme-00036v-ST for ged-emacs-devel@m.gmane.org; Thu, 21 Mar 2013 00:07:20 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:51773) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIWmc-00036o-4K for emacs-devel@gnu.org; Thu, 21 Mar 2013 00:07:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIWma-0000GY-QN for emacs-devel@gnu.org; Thu, 21 Mar 2013 00:07:18 -0400 Original-Received: from mail-ve0-f169.google.com ([209.85.128.169]:53925) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIWma-0000G8-Lg for emacs-devel@gnu.org; Thu, 21 Mar 2013 00:07:16 -0400 Original-Received: by mail-ve0-f169.google.com with SMTP id 15so2145659vea.0 for ; Wed, 20 Mar 2013 21:07:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=r3ncuhXQtCS2kHn+Vmy8Ym4PJwKFdwT94gMJZ7WsXso=; b=JWehHh+4VK1v68IhhtxCc2Nmd8TROjTu/C8l7J7OIruG4L2TyQZJhnFuHsSMPQjvcr nRc603oUaXueX+wCYru19EETPguOyi0CyFWZysuxvo1++8mqV6UJNi2qStz/2h0PFOYa 6y86UkX/8O9liAUG0CREvNKKg1Z3V/XYm0ydSc2PK+UE9fzspsRjg/ZuGpwfT246qdPw E3p/E1B/Ozd9kFFdpUNmncEr9DKzPFwoYoYzW1ZxBJWgpPPT1zjRW5VfN2rrGZUXOpMN 3RxR4WI5bC2PP7fgODkXohE2z68iFFQqkmALMD143JoQMdxQh6+xNy0gQ718ERh5doxO PNeg== X-Received: by 10.52.99.42 with SMTP id en10mr9815806vdb.37.1363838836300; Wed, 20 Mar 2013 21:07:16 -0700 (PDT) Original-Received: from [192.168.1.201] (pool-72-74-140-235.bstnma.fios.verizon.net. [72.74.140.235]) by mx.google.com with ESMTPS id tb9sm665119veb.6.2013.03.20.21.07.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Mar 2013 21:07:15 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a1pre) Gecko/20091222 Shredder/3.1a1pre In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.128.169 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:158020 Archived-At: On 03/20/2013 11:27 PM, Stefan Monnier wrote: >> My initial experiments show I'm on the right track. >> David, is there something that needs merging from Emacs to CEDET I need to >> worry about before making massive structural changes in EIEIO? > > The EIEIO in Emacs has my renaming patch (which fixes some of the > namespace issues, tho it's only a first step). > > Maybe it would make sense to make this change on Emacs's side only. > And to split EIEIO from CEDET (you can distribute an "old EIEIO" for > users of CEDET on older Emacsen that came without EIEIO). Hmmm, well, I managed to split EIEIO to no longer use eval-and-compile, and it is passing my unit tests, but not my integration tests. I made CEDET branch with this change in it in case someone wants to play with it. http://cedet.bzr.sourceforge.net/bzr/cedet/code/eieiosplit/files/head%3A/lisp/eieio/ Getting the integration tests to pass is more than I have time for tonight though. >> If the goal is to use EDE's detection scheme and data, but not load EDE >> project classes, then we are all set already since the EDE project classes >> are not directly involved in detecting the projects. If the goal is to not >> use EIEIO at all, then we'd end up just using a plist other random data >> structure instead of using EIEIO to do it. This wouldn't be a big deal >> because AFAIK, these classes aren't subclassed, so impact would be small. > > I'mnot sure I understand exactly what you're saying, but IIUC you're > saying that there's not much to do to delay EDE loading, and we could > even delay loading of EIEIO with a few code changes. Correct > That sounds promising and confirms my intuition. > >> Alternately, perhaps I can find out why EIEIO isn't acceptable, and fix >> that instead. > > Preloading EIEIO and EDE is not something I'm ready to do. Even just > preloading EIEIO is not something I'm ready to do either. Is this stating that the goal is for project detection to be part of Lisp code that is dumped with Emacs? > I haven't started to think about why, but I'm pretty sure EDE is out of > the question for now. For EIEIO, maybe we could take a look at what it > would entail to see under which circumstances it would be acceptable, > but first it'd need to be namespace clean. > >> From what you say above, it's probably easier to change EDE to not use > EIEIO for the data used for project-detection, before EDE is > actually loaded. If we are talking about what gets dumped out with Emacs, I agree. Eric