News for hackers. Stuff that matters.
Re:How to interpret complex C/C++ declarations (2004) by ajarmst on Thursday August 01, 2013 @04:16AM (#6139190)
Doesn't mention the standard "read it backwards to get the type", and consequently recommends "const int" over the superior "int const".

int * const p;

Is clearly a pointer to pointer to constant pointer to int. (Hint: read from right to left). This is made easier if you always put the const modifier to the right when it is optional.

And just never, ever mix commas with pointer declarations.

Re:How to interpret complex C/C++ declarations (2004) by anonymous on Thursday August 01, 2013 @04:21AM (#6139207)
HN ate your \* symbols. Try prefixing the line with 4 spaces to trigger code formatting.
Re:How to interpret complex C/C++ declarations (2004) by ajarmst on Thursday August 01, 2013 @04:19AM (#6139200)
Not sure why the comment editor trashed "int * const * * p"