old-style backquotes warnings

old-style backquotes warnings

[Eli Zaretskii]

Why doesn't this warning follow the format of other warnings emitted
by the byte compiler?

    Compiling progmodes/cc-subword.el
    !! File cc-vars.el uses old-style backquotes !!

Re: old-style backquotes warnings

[Stefan Monnier]

> Why doesn't this warning follow the format of other warnings emitted
> by the byte compiler?

>     Compiling progmodes/cc-subword.el
>     !! File cc-vars.el uses old-style backquotes !!

Probably because I don't know what's the normal format.


        Stefan

Re: old-style backquotes warnings

[Eli Zaretskii]

> Cc: emacs-devel@gnu.org
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sun, 09 Sep 2007 15:34:35 -0400
> 
> > Why doesn't this warning follow the format of other warnings emitted
> > by the byte compiler?
> 
> >     Compiling progmodes/cc-subword.el
> >     !! File cc-vars.el uses old-style backquotes !!
> 
> Probably because I don't know what's the normal format.

I hope this is a joke (though it's way too far from April 1st),
because I think you wrote the code that produces the normal format,
e.g.:

  In end of data:
  net/browse-url.el:1555:1:Warning: the following functions are not known to be
      defined: copy-seq, w3-fetch-other-window, w3-fetch, case, otherwise

In other words a format that `next-error' can parse.

Re: old-style backquotes warnings

[Stefan Monnier]

>> > Why doesn't this warning follow the format of other warnings emitted
>> > by the byte compiler?
>> 
>> >     Compiling progmodes/cc-subword.el
>> >     !! File cc-vars.el uses old-style backquotes !!
>> 
>> Probably because I don't know what's the normal format.

> I hope this is a joke (though it's way too far from April 1st),
> because I think you wrote the code that produces the normal format,
> e.g.:

>   In end of data:
>   net/browse-url.el:1555:1:Warning: the following functions are not known to be
>       defined: copy-seq, w3-fetch-other-window, w3-fetch, case, otherwise

> In other words a format that `next-error' can parse.

Oh sorry, now I see it: the warning you talk about is the one from Fload (a
call to Fmessage), not the one from the byte-compiler, which is why it
doesn't follow the byte-compiler's format.


        Stefan

Re: old-style backquotes warnings

[Richard Stallman]

    Oh sorry, now I see it: the warning you talk about is the one from Fload (a
    call to Fmessage), not the one from the byte-compiler, which is why it
    doesn't follow the byte-compiler's format.

How about making it call byte-compile-warning when it is done
from inside the byte compiler?

Re: old-style backquotes warnings

[Stefan Monnier]

>     Oh sorry, now I see it: the warning you talk about is the one from
>     Fload (a call to Fmessage), not the one from the byte-compiler, which
>     is why it doesn't follow the byte-compiler's format.

> How about making it call byte-compile-warning when it is done
> from inside the byte compiler?

Is it really worth the trouble?
Check again the message carefully : it's complaining about the use of
old-style backquote in cc-vars.el while compiling the cc-subword.el file.
So it wouldn't be able to give any line-number info anyway.

Furthermore the next-error-compatible warning will be displayed when
cc-vars.el gets compiled.


        Stefan

Re: old-style backquotes warnings

[Richard Stallman]

    Check again the message carefully : it's complaining about the use of
    old-style backquote in cc-vars.el while compiling the cc-subword.el file.
    So it wouldn't be able to give any line-number info anyway.

I didn't understand that aspect of the problem.

How about this message instead:

   Loading `cc-vars.el': old-style backquotes detected.

That makes the relationships explicit
so that a person doesn't have to deduce them from the file names.

Re: old-style backquotes warnings

[Stefan Monnier]

> How about this message instead:

>    Loading `cc-vars.el': old-style backquotes detected.

> That makes the relationships explicit
> so that a person doesn't have to deduce them from the file names.

OK, changed,


        Stefan