[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Towards a cleaner build: other output
From: |
Stefan Monnier |
Subject: |
Re: Towards a cleaner build: other output |
Date: |
Mon, 17 Jun 2019 18:40:24 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> eieio.el: ‘object-print’ is an obsolete generic function (as of 26.1); use
> ‘cl-print-object’ instead.
>
> These are output by cl-defmethod/cl-defgeneric, and we're defining an
> (obsolete) fallback method, so we should suppress this warning. Do we
> need a new mechanism or do we have something to cover this?
Presumably wrapping those `cl-defmethod`s in a with-suppressed-warnings
should do the trick.
> *Warning* default value of <<no-type>> tokens changed to QUERY, was NULL_TOKEN
> *Warning* default value of <<no-type>> tokens changed to TRUE, was QUERY
> *Warning* default value of <<no-type>> tokens changed to FALSE, was TRUE
> Grammar in javascript.el contains 2 useless nonterminals and 4 useless rules
> Grammar in js-wy.el contains 2 useless nonterminals and 4 useless rules
> Grammar in python-wy.el contains 2 useless nonterminals and 3 useless rules
> Grammar in python-wy.el contains 4 shift/reduce conflicts
> Grammar in python.el contains 2 useless nonterminals and 3 useless rules
> Grammar in python.el contains 4 shift/reduce conflicts
>
> These are from cedet, and are warning about grammars containing...
> useless rules? Perhaps this is more useful at run-time than at compile
> time?
This is like running `yacc`: you want those warnings when you run
`yacc`, not when you use the resulting grammar.
> Loading /home/larsi/src/emacs/trunk/lisp/international/uni-name.el (source)...
>
> Hm... a "Loading" in the middle here? Does anybody know why?
I guess something's using `load` instead of `require`?
> latin-ltx: 1535 rules (+ 0 conflicts)!
> Uhm... That doesn't seem very useful to me -- only output that if there
> are any conflicts?
Agreed (and I plead guilty),
Stefan
- Re: Towards a cleaner build: other output, (continued)
- Re: Towards a cleaner build: done!, Lars Ingebrigtsen, 2019/06/20
- Re: Towards a cleaner build: done!, Noam Postavsky, 2019/06/20
- Re: Towards a cleaner build: done!, Lars Ingebrigtsen, 2019/06/20
- Re: Towards a cleaner build: done!, Eli Zaretskii, 2019/06/22
- Re: Towards a cleaner build: done!, Arash Esbati, 2019/06/25
- Re: Towards a cleaner build: done!, Lars Ingebrigtsen, 2019/06/25
- Re: Towards a cleaner build: other output, Eli Zaretskii, 2019/06/18
- Re: Towards a cleaner build: other output,
Stefan Monnier <=
- Re: Towards a cleaner build: other output, Lars Ingebrigtsen, 2019/06/17
- Re: Towards a cleaner build: other output, Lars Ingebrigtsen, 2019/06/18
- Re: Towards a cleaner build: other output, Stefan Monnier, 2019/06/18
- Re: Towards a cleaner build: other output, Lars Ingebrigtsen, 2019/06/18
- Re: Towards a cleaner build: other output, Lars Ingebrigtsen, 2019/06/18
- Re: Towards a cleaner build: other output, Stefan Monnier, 2019/06/18
- Re: Towards a cleaner build: other output, Lars Ingebrigtsen, 2019/06/18
- Re: Towards a cleaner build: viper-ex, Lars Ingebrigtsen, 2019/06/12
- Re: Towards a cleaner build: project.el, Lars Ingebrigtsen, 2019/06/12
- Re: Towards a cleaner build: obsolete/cl-compat.el, Lars Ingebrigtsen, 2019/06/12