From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: maintain flymake.el Date: Mon, 16 Dec 2013 17:06:33 +0100 Message-ID: References: <87a9gdzx63.fsf@flea.lifelogs.com> <8738lsq32g.fsf@flea.lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1387210009 13334 80.91.229.3 (16 Dec 2013 16:06:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Dec 2013 16:06:49 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 16 17:06:56 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 1Vsah4-0005M6-30 for ged-emacs-devel@m.gmane.org; Mon, 16 Dec 2013 17:06:54 +0100 Original-Received: from localhost ([::1]:56808 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vsah3-0006Jn-Ad for ged-emacs-devel@m.gmane.org; Mon, 16 Dec 2013 11:06:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vsagv-0006DY-Jz for emacs-devel@gnu.org; Mon, 16 Dec 2013 11:06:50 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vsagp-00054n-Vz for emacs-devel@gnu.org; Mon, 16 Dec 2013 11:06:45 -0500 Original-Received: from mailfe02.swip.net ([212.247.154.33]:38106 helo=swip.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vsagp-000549-PG for emacs-devel@gnu.org; Mon, 16 Dec 2013 11:06:39 -0500 X-T2-Spam-Status: No, hits=0.0 required=5.0 Original-Received: from hosdjarv.se (account mj138573@tele2.se [46.59.42.57] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 461750188 for emacs-devel@gnu.org; Mon, 16 Dec 2013 17:06:34 +0100 In-Reply-To: <8738lsq32g.fsf@flea.lifelogs.com> X-Mailer: Apple Mail (2.1822) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 212.247.154.33 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:166479 Archived-At: Hello. 16 dec 2013 kl. 15:32 skrev Ted Zlatanov : > On Sun, 15 Dec 2013 19:31:46 +0100 Sebastian Wiesner = wrote:=20 >=20 > SW> 2013/12/14 Sebastian Wiesner : >>> I hope to finish the document by tomorrow evening, and will come = back >>> if it's done. >=20 > SW> I have completed the document now. The final version is to be = found > SW> at = https://github.com/flycheck/flycheck/wiki/Flycheck-versus-Flymake. > SW> It's a thorough write-up of the differences and similarities = between > SW> Flycheck and Flymake, and probably also a comprehensive summary of = the > SW> current issues and weaknesses in Flymake. >=20 > SW> Again, it's probably unfairly biased towards Flycheck. I tried my > SW> best to be neutral, but I consider Flycheck superior and think = that > SW> the design and implementation of Flymake are somewhat broken, so I = may > SW> have failed to properly account for Flymake's features and = strengths. > SW> Please excuse this, and feel free to correct any mistakes I may = have > SW> made. >=20 > SW> Please also suggest improvements, such as additional aspects which > SW> should be covered, or report issues, such as missing details in = the > SW> comparsion. You are missing the big think that separates flymake and flycheck. = Flymake uses makefiles, flycheck does not. This means to be able to use = flycheck on a large C/C++ project you have to maintain includes and = defined in both makefiles and as lisp variables for flycheck. Flymake = does not have that problem, you just add one rule for it in the = makefiles, re-using all definitions and include paths. This is really a showstopper for flycheck, even if it has some nicer GUI = stuff. It is really only usable for small projects. Disclaimer: This might have changed since I last checked. Jan D.