From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Thu, 08 Jan 2015 17:21:02 +0200 Message-ID: <83r3v55me9.fsf@gnu.org> References: <83bnxuzyl4.fsf@gnu.org> <87vbkovhh7.fsf@engster.org> <87387rvobr.fsf@engster.org> <83ppat84hk.fsf@gnu.org> <20150106143933.0090bc83@jabberwock.cb.piermont.com> <83r3v77ij6.fsf@gnu.org> <20150106154539.3d0752c4@jabberwock.cb.piermont.com> <87wq4ype3z.fsf@fencepost.gnu.org> <20150108083211.5a85a077@jabberwock.cb.piermont.com> <877fwxpb63.fsf@fencepost.gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1420730682 24275 80.91.229.3 (8 Jan 2015 15:24:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 8 Jan 2015 15:24:42 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org, deng@randomsample.de, perry@piermont.com To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 08 16:24:35 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 1Y9Etk-0004uo-Vx for ged-emacs-devel@m.gmane.org; Thu, 08 Jan 2015 16:21:21 +0100 Original-Received: from localhost ([::1]:46488 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9Etj-0002YX-0T for ged-emacs-devel@m.gmane.org; Thu, 08 Jan 2015 10:21:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49907) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9EtQ-0002Y2-PU for emacs-devel@gnu.org; Thu, 08 Jan 2015 10:21:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y9EtK-0005d8-Oh for emacs-devel@gnu.org; Thu, 08 Jan 2015 10:21:00 -0500 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:51946) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9EtF-0005bj-GS; Thu, 08 Jan 2015 10:20:49 -0500 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0NHV00G00687J400@mtaout24.012.net.il>; Thu, 08 Jan 2015 17:12:48 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NHV0053U69C9XB0@mtaout24.012.net.il>; Thu, 08 Jan 2015 17:12:48 +0200 (IST) In-reply-to: <877fwxpb63.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.180 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:181064 Archived-At: > From: David Kastrup > Date: Thu, 08 Jan 2015 16:03:16 +0100 > Cc: eliz@gnu.org, emacs-devel@gnu.org, Richard Stallman , > deng@randomsample.de, monnier@iro.umontreal.ca > > We are losing contact with academia, that's true. I don't see a > short-term fix for that. But we are losing also contact with willing > hackers who'd actually want to work on Emacs/GCC integration and who'd > be perfectly willing to just leave the legal considerations in the hand > of the FSF but who are barred from working on the implementation. > > And that's really worrying. I think there's too much baby in the > bathwater we are throwing out here. I agree, but I think we should get back on track discussing the technical issues and aspects of building infrastructure for a good modern IDE using some help from GCC. Suppose we did have a way getting the necessary information from GCC that is not in the form of an AST: what such an information package would need to include to allow the functionality users expect from a modern IDE? Could someone come up with a list of information items that would be needed? Given such a list, we could try to discuss various alternatives of getting the info from GCC.