[dev] dwm alpha patch: const isn't a const??

From: Paul Swanson <psw_AT_protonmail.com>
Date: Sun, 26 May 2019 08:05:40 +0000


I've a fresh clone of dwm and the dwm alpha patch (20180613-b69c870) and it's generating
the following error:

        In file included from dwm.c:280:0:
        config.h:24:27: error: initializer element is not constant
          [SchemeNorm] = { OPAQUE, baralpha, borderalpha },
        config.h:24:27: note: (near initialization for ‘alphas[0][1]’)
        config.h:24:37: error: initializer element is not constant

What I can't understand, is the fact that 'baralpha', and all the other variables
accused of not being constants are in fact declared as "static const unsigned int":

            static const unsigned int baralpha = 0xd0;
            static const unsigned int borderalpha = OPAQUE;

If I substitute the initialising variables for a numeric literal (ie. 1) it compiles.
But if I leave the constants from the patch or make my own, it fails.

How can a const, not be a const?

Any help would be greatly appreciated.


Paul Swanson

Sent from ProtonMail, encrypted email based in Switzerland.
Received on Sun May 26 2019 - 10:05:40 CEST

This archive was generated by hypermail 2.3.0 : Sun May 26 2019 - 10:24:08 CEST