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: byte-compiler does *not* complain about missing case or loop Date: Mon, 10 Mar 2014 00:33:21 -0400 Message-ID: References: <87siqwslfm.fsf@gmail.com> <878uslmkq1.fsf@gmail.com> <87iornmo76.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1394426015 15668 80.91.229.3 (10 Mar 2014 04:33:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Mar 2014 04:33:35 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jambunathan K Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 10 05:33:41 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 1WMruG-0001kZ-JD for ged-emacs-devel@m.gmane.org; Mon, 10 Mar 2014 05:33:40 +0100 Original-Received: from localhost ([::1]:46646 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMruG-0003zu-7K for ged-emacs-devel@m.gmane.org; Mon, 10 Mar 2014 00:33:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42623) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMru6-0003zf-A8 for emacs-devel@gnu.org; Mon, 10 Mar 2014 00:33:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WMrtz-0004a2-0G for emacs-devel@gnu.org; Mon, 10 Mar 2014 00:33:30 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:52771) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMrty-0004Zy-SY for emacs-devel@gnu.org; Mon, 10 Mar 2014 00:33:22 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFMCppy/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IPAS-Result: Av4EABK/CFFMCppy/2dsb2JhbABEvw4Xc4IeAQEEAVYjEAs0EhQYDSSIHgbBLZEKA6R6gV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="50966197" Original-Received: from 76-10-154-114.dsl.teksavvy.com (HELO ceviche.home) ([76.10.154.114]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 10 Mar 2014 00:33:22 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id D719F660A5; Mon, 10 Mar 2014 00:33:21 -0400 (EDT) In-Reply-To: <87iornmo76.fsf@gmail.com> (Jambunathan K.'s message of "Sun, 09 Mar 2014 20:08:53 +0530") 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.181 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:170242 Archived-At: >>> 1. The compiler doesn't get to "the end of data" ritual. >> No, because it hits an actual error and just stops there, without even >> generating a .elc file. > Should it stop just there? You mean, should it have better "error recovery"? I'd agree that it would be better if it could recover in such a case. But I think I'd only accept a patch for it if it can be implemented in a simple/clean way, because the benefit is fairly small. Stefan