[debbugs-tracker] bug#12371: closed (24.2.50; macroexpand-all reporting warnings to *Compile-Log*)

[GNU bug Tracking System]

Your message dated Thu, 20 Sep 2012 10:16:12 -0400
with message-id <address@hidden>
and subject line Re: bug#12371: macroexp--funcall-if-compiled broke bootstrap 
for me
has caused the debbugs.gnu.org bug report #12371,
regarding 24.2.50; macroexpand-all reporting warnings to *Compile-Log*
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
12371: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12371
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.2.50; macroexpand-all reporting warnings to *Compile-Log*
>
>
>
>
> Date: 
>
> Thu,  6 Sep 2012 14:58:22 +0100 (BST)
>
>
>
>
> emacs -q
> M-: (macroexpand-all '(mapc '(lambda ()) nil)) RET
>
> Debugger entered--Lisp error: (void-function byte-compile-log-warning)
>
> emacs -q
> M-x load-library RET bytecomp RET
> M-: (macroexpand-all '(mapc '(lambda ()) nil)) RET
>
> A *Compile-Log* buffer appears, with the following content
>
>     Warning: (lambda nil ...) quoted with ' rather than with #'
>
> This is utterly confusing.  There is no compilation going on.  (Another
> user experience regarding this issue can be found in bug report 12362 -
> <address@hidden>.)
>
> macroexp--expand-all, which is the originator of the warning, calls
> byte-compile-log-warning without consulting byte-compile-warnings.
>
> I think the warning message should include a hint that it was generated
> by macroexpanding code and byte-compile-warnings should be consulted as
> well.
>
> GNU Emacs 24.2.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of
> 2012-09-06.
>
>         Christopher
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#12371: macroexp--funcall-if-compiled broke bootstrap for me
>
>
>
>
> Date: 
>
> Thu, 20 Sep 2012 10:16:12 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)
>
>
>
>
> >> The first one I think just is a line gone missing.
> > No, I removed that line on purpose (an autoload entry shouldn't have
> > a nil in position 1, so it should be a redundant test).
>
> That was a brain malfunction, sorry.  Should be fixed now.
>
> >> The next chunk extracts (car form) before it's to late, as form goes
> >> about being changed before the closure is being called.
> > Duh, sorry 'bout that.  Please install your patch,
>
> I actually installed a different patch instead, which does what your did
> plus removes a FIXME.
>
>
>         Stefan
>
>
> --- End Message ---