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: A unified project root interface Date: Wed, 20 Mar 2013 23:27:08 -0400 Message-ID: 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 X-Trace: ger.gmane.org 1363836446 27666 80.91.229.3 (21 Mar 2013 03:27:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Mar 2013 03:27:26 +0000 (UTC) Cc: Jorgen Schaefer , John Yates , David Engster , emacs-devel@gnu.org To: "Eric M. Ludlam" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 21 04:27:52 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 1UIWAR-000448-Bv for ged-emacs-devel@m.gmane.org; Thu, 21 Mar 2013 04:27:51 +0100 Original-Received: from localhost ([::1]:46125 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIWA3-00049O-Tf for ged-emacs-devel@m.gmane.org; Wed, 20 Mar 2013 23:27:27 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:44717) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIWA0-00049H-PV for emacs-devel@gnu.org; Wed, 20 Mar 2013 23:27:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIW9w-0004Mc-Pd for emacs-devel@gnu.org; Wed, 20 Mar 2013 23:27:24 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:41887) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIW9w-0004MW-Le for emacs-devel@gnu.org; Wed, 20 Mar 2013 23:27:20 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFFxKvA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOfYQSFFYFegxM X-IPAS-Result: Av4EABK/CFFFxKvA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOfYQSFFYFegxM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="5412959" Original-Received: from 69-196-171-192.dsl.teksavvy.com (HELO pastel.home) ([69.196.171.192]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 20 Mar 2013 23:27:13 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 0AAE167AF3; Wed, 20 Mar 2013 23:27:09 -0400 (EDT) In-Reply-To: <514A5A68.3070907@siege-engine.com> (Eric M. Ludlam's message of "Wed, 20 Mar 2013 20:55:04 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:158018 Archived-At: > 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). > 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. That sounds promising and confirms my intuition. > In both cases above, we'd need a simple mechanism to disable the loading of > EDE project classes, and using a placeholder in the project cache instead. Sot sure what you're saying here. > 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. 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. Stefan