News for hackers. Stuff that matters.
Re:A convenient untruth: Array notation in C is a lie by bluetomcat on Thursday December 22, 2016 @12:27PM (#13238751)
> Surely it would still mirror use if the operators were applied to the type, rather than the identifier?

The "type" is actually a list of storage class specifiers (static, extern, auto, register, typedef, _Thread_local), type qualifiers (const, volatile, restrict) and type specifiers (int, char, float, double, signed, unsigned, long, short, void). Imagine the soup of keywords that would have to be at the deepest level of the expression:

    static const volatile unsigned char *arr[X];
    // vs
    *static const volatile unsigned char[X] arr;
Re:A convenient untruth: Array notation in C is a lie by Nullabillity on Thursday December 22, 2016 @07:37PM (#13241825)
static, const, and volatile modify the variable itself, not what values it's legal for it to contain. So the outcome should be:

    static const volatile *unsigned char[X] arr;
Or, because signedness should be a property of the type, not an arbitrary modifier:

    static const volatile *char[X] arr;