🚀 go-pugleaf

Markus Stumptner writes:

>As for the comments on the cryptic C syntax - yes, it is harder to
>read.  Reading speed is not measured in characters, but words;
>cognitively, word shapes have a lot to do with recognizing a word, and
>moderately long keywords separated by whitespaces are easier to read
>than bunched-together special characters (don't remember where I read
>that, though).

Yeah, C is sometimes very hard to read.  I guess it is all a mater of
what you are used to.  I learned C about five years ago, and I remember
being confused quite frequently.  Things like this I still have to look
at for a while:

void Garply (void (*foo) (void (*bar) (void (*baz) (void))));

This is a function prototype for a function called Garply, it returns
void and takes as it's argument foo, which is a pointer to a function which 
returns void and takes as it's argument bar, which is a pointer to a function 
which returns void and takes as it's argument baz, which is a pointer to a
function which returns void and takes void as it's argument.

This prototype could have also been written like this:

void Garply (void (*) (void (*) (void (*) (void))));

This is of course ANSI C.  If you try stuff like this on a non-ANSI
compiler I would expect it to yak.
--