Greetings.
On Mon, 18 Jul 2016 18:33:06 +0200 Paul Menzel <pmenzel_AT_molgen.mpg.de> wrote:
> Dear FRIGN,
>
>
> On 07/18/16 14:49, FRIGN wrote:
> > On Mon, 18 Jul 2016 14:45:44 +0200 Paul Menzel wrote:
>
> >> If I am not mistaken, this is really a corner case. The user has to
> >> set `actionfps` to zero in `config.def.h`.
> >>
> >> ```
> >> config.def.h:static unsigned int actionfps = 30;
> >> ```
> >>
> >> Even setting it to zero and rebuilding the package, I was unable to
> >> trigger the issue.
> >
> > why would you set actionfps to 0? Thing is, what users do in config.h
> > is their responsibility. I could also leave a struct empty and then
> > be "surprised" about the program breaking. What you configure in
> > config.h is your responsibility, that's it.
>
> I can understand that reasoning. On the other hand, mistakes can happen,
> so having checks for sensible values and inform the user about it, might
> be a good idea.
Thanks for sending in this clang bug report. The main way to fix it is
to not use clang. If you find some way to make this warning disappear,
please let me know, so I will apply it to st.
config.h value checking is against the ethics and morals of suckless.
Users should be able to shoot into their foot very hard. The harder the
better they learn.
Sincerely,
Christoph Lohmann
Received on Mon Jul 18 2016 - 18:33:06 CEST