unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Yuta Yamada <sleepboy.zzz@gmail.com>
Cc: 23495@debbugs.gnu.org
Subject: bug#23495: byte-compile-file return t when there is "XXX can't use lexical var" error
Date: Wed, 11 May 2016 13:57:39 +0200	[thread overview]
Message-ID: <87vb2k6c3w.fsf@web.de> (raw)
In-Reply-To: <87shxpigij.fsf@web.de> (Michael Heerdegen's message of "Wed, 11 May 2016 02:29:24 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Seems it's wanted.  The compiler calls `byte-compile-log-warning' in
> this case, which, unlike `byte-compile-warn', circumvents
> `byte-compile-error-on-warn'.

I wonder if we could/should call `byte-compile-warn' instead.

But Yuta, please tell me about your use case.  A lot of other warnings
printed while byte compiling can hint to similarly serious mistakes in
the code.

Would changing the behavior of this particular case really make things
better?  Can't you just have a look at the compiler warnings, which is a
good idea (necessary) anyway?


Thanks,

Michael.





  reply	other threads:[~2016-05-11 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  8:12 bug#23495: byte-compile-file return t when there is "XXX can't use lexical var" error Yuta Yamada
2016-05-10 18:23 ` Michael Heerdegen
2016-05-10 23:45   ` Yuta Yamada
2016-05-11  0:29     ` Michael Heerdegen
2016-05-11 11:57       ` Michael Heerdegen [this message]
2016-05-11 14:33         ` Yuta Yamada
2016-05-11 16:25           ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vb2k6c3w.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=23495@debbugs.gnu.org \
    --cc=sleepboy.zzz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).