suppressable byte compilation warnings and cconv.el

suppressable byte compilation warnings and cconv.el

[Paul Pogonyshev]

In file `bytecomp.el' there is a customizable variable
`byte-compile-warnings' that allows one to selectively silence certain
warnings. However, functions in `cconv.el' don't make use of that at
all, their warnings are unconditionally printed.

In particular, I'm annoyed by warnings like this:

    Warning: Unused lexical argument ‘size’

I can create a patch to make some warnings in `cconv.el' suppressable
too. Does that sound like a good idea?

Paul

Re: suppressable byte compilation warnings and cconv.el

[Stefan Monnier]

> In file `bytecomp.el' there is a customizable variable
> `byte-compile-warnings' that allows one to selectively silence certain
> warnings.

I wouldn't use the word "selectively" to describe it.
It's extremely coarse only allowing you to control broad categories of
errors file-wide.

> In particular, I'm annoyed by warnings like this:
>     Warning: Unused lexical argument ‘size’

You can silence those (and yes, selectively this time) by prefixing the
variable name with an underscore, which makes it explicit that you know
the variable is not used.


        Stefan

Re: suppressable byte compilation warnings and cconv.el

[Paul Pogonyshev]

> You can silence those (and yes, selectively this time) by prefixing the
> variable name with an underscore, which makes it explicit that you know
> the variable is not used.

Yes, I know about that, but that means you have to go about each
individual warning in every function. And remember to rename
parameters by adding/removing underscore when usage inside the
function changes. I'd like to also have the ability to silence all
such warnings altogether.

Paul

On 14 April 2016 at 03:35, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> In file `bytecomp.el' there is a customizable variable
>> `byte-compile-warnings' that allows one to selectively silence certain
>> warnings.
>
> I wouldn't use the word "selectively" to describe it.
> It's extremely coarse only allowing you to control broad categories of
> errors file-wide.
>
>> In particular, I'm annoyed by warnings like this:
>>     Warning: Unused lexical argument ‘size’
>
> You can silence those (and yes, selectively this time) by prefixing the
> variable name with an underscore, which makes it explicit that you know
> the variable is not used.
>
>
>         Stefan
>
>

Re: suppressable byte compilation warnings and cconv.el

[Paul Pogonyshev]

To clarify why I want it.  I have some procedurally generated
functions, which I byte-compile after generation.  I would like to
avoid renaming attributes in the generator (not to mention the logic
needed to detect whether they are used), instead I'd just temporarily
suppress "unused x" warnings during this particular byte compilation.

Paul

On 14 April 2016 at 09:49, Paul Pogonyshev <pogonyshev@gmail.com> wrote:
>> You can silence those (and yes, selectively this time) by prefixing the
>> variable name with an underscore, which makes it explicit that you know
>> the variable is not used.
>
> Yes, I know about that, but that means you have to go about each
> individual warning in every function. And remember to rename
> parameters by adding/removing underscore when usage inside the
> function changes. I'd like to also have the ability to silence all
> such warnings altogether.
>
> Paul
>
> On 14 April 2016 at 03:35, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>> In file `bytecomp.el' there is a customizable variable
>>> `byte-compile-warnings' that allows one to selectively silence certain
>>> warnings.
>>
>> I wouldn't use the word "selectively" to describe it.
>> It's extremely coarse only allowing you to control broad categories of
>> errors file-wide.
>>
>>> In particular, I'm annoyed by warnings like this:
>>>     Warning: Unused lexical argument ‘size’
>>
>> You can silence those (and yes, selectively this time) by prefixing the
>> variable name with an underscore, which makes it explicit that you know
>> the variable is not used.
>>
>>
>>         Stefan
>>
>>

Re: suppressable byte compilation warnings and cconv.el

[Stefan Monnier]

> To clarify why I want it.  I have some procedurally generated
> functions, which I byte-compile after generation.

For those cases where you don't actually know whether it's used or not
(most typically this happens in macros), you can instead use the
`ignore' function:

   (defun foo (arg1 arg2)
     (ignore arg1 arg2)
     ...)


-- Stefan

Re: suppressable byte compilation warnings and cconv.el

[Paul Pogonyshev]

> For those cases where you don't actually know whether it's used or not
> (most typically this happens in macros), you can instead use the
> `ignore' function

OK, good enough for my usecase. Thank you.

Paul

On 14 April 2016 at 14:04, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> To clarify why I want it.  I have some procedurally generated
>> functions, which I byte-compile after generation.
>
> For those cases where you don't actually know whether it's used or not
> (most typically this happens in macros), you can instead use the
> `ignore' function:
>
>    (defun foo (arg1 arg2)
>      (ignore arg1 arg2)
>      ...)
>
>
> -- Stefan