From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Ludlam Newsgroups: gmane.emacs.devel Subject: Re: Is EDE only intended to be used with languages which /require/ a 'compile' step? [was: Re: IDE] Date: Sat, 17 Oct 2015 10:09:47 -0400 Message-ID: <562256AB.4010906@siege-engine.com> References: <5610207A.2000300@harpegolden.net> <83fv1r3gzp.fsf@gnu.org> <83bncf3f9k.fsf@gnu.org> <5610E0BC.8090902@online.de> <83si5r106e.fsf@gnu.org> <831td9z18h.fsf@gnu.org> <5612E996.7090700@yandex.ru> <83bnc7tavr.fsf@gnu.org> <5618C92A.3040207@yandex.ru> <83a8rrt9ag.fsf@gnu.org> <5618D376.1080700@yandex.ru> <831td3t62e.fsf@gnu.org> <561A6199.1020901@cumego.com> <561B9D87.70504@yandex.ru> <561C2C17.3090503@cumego.com> <561DC1CA.6090901@siege-engine.com> <561E3FB6.8010407@yandex.ru> <561EEFDE.7000809@gmail.com> <561F29D0.3070605@yandex.ru> <561FA79C.30207@gmail.com> <56200D07.30206@yandex.ru> <5620A99E.7080009@cumego.com> <5621AE14.8040004@gmail.com> <878u72tbw4.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1445091023 17227 80.91.229.3 (17 Oct 2015 14:10:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 Oct 2015 14:10:23 +0000 (UTC) To: Alexis , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 17 16:10:15 2015 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 1ZnSBa-0003p0-SS for ged-emacs-devel@m.gmane.org; Sat, 17 Oct 2015 16:10:15 +0200 Original-Received: from localhost ([::1]:58443 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnSBZ-00009n-Oj for ged-emacs-devel@m.gmane.org; Sat, 17 Oct 2015 10:10:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51236) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnSBF-00007q-8J for emacs-devel@gnu.org; Sat, 17 Oct 2015 10:09:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZnSBB-0004Tm-Tt for emacs-devel@gnu.org; Sat, 17 Oct 2015 10:09:53 -0400 Original-Received: from mail-qg0-f48.google.com ([209.85.192.48]:33191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnSBB-0004TX-PV for emacs-devel@gnu.org; Sat, 17 Oct 2015 10:09:49 -0400 Original-Received: by qgeo38 with SMTP id o38so79329368qge.0 for ; Sat, 17 Oct 2015 07:09:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=4NbCa9S1HGrwXrNBxu00VMcSvQxFhZh5yMgr9t5Ttmg=; b=K2NOLIenMSq7p/bqfPLM4Mh9EsYg+FdLfU1G8HXgbPMcfOt3TRcTs98QTpeIzsbgrk 0wF17FW9RKwEBAuRumJlJDgXUFpgiuPv1PmndY5+B9r3V4b8Ul2t20ijQ4q+FtPKwPPX Xfjb1qILrTajsjVGG290dbjmpGztmXFkzHQRZX360h4ZAFIQkYD4ZVqg/yYL0m5xn7Bx LXVn7OuScLkdQC2z2MRA1HvGwpIwjegNJWW8UcwRuZVjYHrOOiY6Kh/fSF2j4o2Wfldn iJgXsixQljCPDynjteZ06Et5jTHXRv897AUTmaZAdWLDt5NhIaXr7IAODLrtH1Dpr60S BviA== X-Received: by 10.140.217.70 with SMTP id n67mr27015743qhb.96.1445090989226; Sat, 17 Oct 2015 07:09:49 -0700 (PDT) Original-Received: from [192.168.1.202] (pool-71-184-198-118.bstnma.fios.verizon.net. [71.184.198.118]) by smtp.googlemail.com with ESMTPSA id 139sm9992472qhh.43.2015.10.17.07.09.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Oct 2015 07:09:48 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 In-Reply-To: <878u72tbw4.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.192.48 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:191828 Archived-At: On 10/16/2015 11:24 PM, Alexis wrote: > > Eric Ludlam writes: > >> EDE's framework starts with no assumptions about anything other than a >> basic "compile", and letting the project implementation populate it. > > It seems to me that this assumption only holds for programming languages > which require a distinct compile step in order to produce an executable > program. If EDE isn't intended to be used with languages such as Python, > JavaScript, Ruby, Lua, Perl etc., fair enough - but this should be made > clear in this discussion and in the EDE documentation, so that > developers/users wanting an Emacs-based software project management > system for such languages can focus attention/efforts elsewhere (e.g. > Projectile, project.el). EDE's original intent was for handling compilation of compiled languages. Since then, it also forms a base for anything that wants to organize code into a 'project' so that support code can say "what is the current project" and then "does that project have a language specific detail I can use". It doesn't really matter if it compiles or not. If your specific language has no need of a centralized project info, then sure, it won't need EDE. If python, JS or whatever may need different information such as include paths, browser to connect to from Emacs, etc, then that could be wrapped up in EDE. The advantage would be a consistent way to think about each step in using the project. Your C++ project may have entirely different steps in the workflow than javascript, but users would know to look into the Development menu to see what that project can do. In addition, EDE, plus other parts such as Semantic or SRecode provide project and language independent ways to get at basic questions, so tools like ECB or Speedbar can display information independent of language. The more language specific the request, the harder that is of course, but having one place to get at the data makes writing those tools easier. Eric