From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Wed, 26 Feb 2014 20:53:57 +0100 Message-ID: <87sir5ejl6.fsf@engster.org> References: <87wqgr4v18.fsf@yandex.ru> <53064BD0.7070009@yandex.ru> <87ha7tr5bo.fsf@fencepost.gnu.org> <87ppmhecd8.fsf@yandex.ru> <87y50z90pd.fsf@fencepost.gnu.org> <87txbn8r6x.fsf@fencepost.gnu.org> <8338j717oe.fsf@gnu.org> <87zjlf6tdx.fsf@fencepost.gnu.org> <83sir7yue7.fsf@gnu.org> <8761o3dlak.fsf@wanadoo.es> <83bnxuzyl4.fsf@gnu.org> <871tyqes5q.fsf@wanadoo.es> <87a9ddg7o8.fsf@engster.org> <87txbld5kr.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1393444455 26505 80.91.229.3 (26 Feb 2014 19:54:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Feb 2014 19:54:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 26 20:54:24 2014 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 1WIkYf-000877-Gj for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 20:54:21 +0100 Original-Received: from localhost ([::1]:43034 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIkYf-00070t-5v for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 14:54:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37992) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIkYW-0006tH-Fa for emacs-devel@gnu.org; Wed, 26 Feb 2014 14:54:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIkYO-0005yY-Dg for emacs-devel@gnu.org; Wed, 26 Feb 2014 14:54:12 -0500 Original-Received: from randomsample.de ([5.45.97.173]:53028) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIkYO-0005vN-3Y for emacs-devel@gnu.org; Wed, 26 Feb 2014 14:54:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=R60CPODVD73ArW1stGvuafcKa8Ir6h6xaRy9LFN+n9A=; b=bHq8LvD/9aIqyy6tj+UZ0P94x/XnOfOkpwxOHyoBOE9FV7BDLivY0loxHjtEu1UBIVJvzVa1X70BNiY7kNWldfEDgOTq269+RpDoqW4GgUFZ9DKfmRYqFaenjs1cF7/Q; Original-Received: from dslc-082-083-054-035.pools.arcor-ip.net ([82.83.54.35] helo=spaten) by randomsample.de with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1WIkYM-0007sW-8l; Wed, 26 Feb 2014 20:54:02 +0100 In-Reply-To: <87txbld5kr.fsf@wanadoo.es> (=?iso-8859-1?Q?=22=D3scar?= Fuentes"'s message of "Wed, 26 Feb 2014 20:41:56 +0100") User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux) Mail-Followup-To: =?iso-8859-1?Q?=D3scar?= Fuentes , emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 5.45.97.173 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:169891 Archived-At: =D3scar Fuentes writes: > ... it works just by chance. You are really fast at dismissing things. >> That should not >> be very hard to add, but - as usual - someone has to do it. > > Overload resolution is one of the most difficult parts of "C++ with > classes" (the language without templates). Another very tricky part is > namespace resolution. Thanks for the lecture. > Just because current solutions are no 100% accurate doesn't mean that > the feature should be ignored. Until recently, those solutions falled > into two classes: "heroic" parsers (i.e. Eclipse's) and compilers acting > as analyzers (MS Visual Studio, which uses a propietary compiler > front-end (not their own)) inspecting its internal state. The former is > absolutely insufficient and the later is like using an square peg in a > round hole, because the compiler was never intended to do that (same > could be said of GCC.) Clang is changing all that because it is designed > from the start for making available and manageable the required > information. Then by all means go ahead with whatever you are proposing. -David