Coding Style Irony

In light of this,

From: [OMITTED]
Sent: Thursday, May 23, 2013 7:10 PM
To: Thomas M. Tuerke
Subject: commas and spaces

Please put a space after commas, e.g. “foo(a, b, c)” rather than “foo(a,b,c)”.

Thanks.

From: [OMITTED]
Sent: Thursday, May 23, 2013 7:12 PM
To: Thomas M. Tuerke
Subject: while we're on the subject of whitespace...

Please put spaces around “usual” binary operators, e.g. “a + b” rather than “a+b” (but “p . q” or “p -> q”).

Thanks, again.

I observe in response:

 Egyptian braces on a function block;
   Newlines on formal params really rock!
 Code that wanders to the right, unseen.
   Monster functions, screen after screen!

 But man-oh-man, in all those places,
    make sure binops have their spaces!

 Names_in_lowercase_with_scores_between,
   mixedWithCamelCaseCanBeSeen.
 Naked functions—whence they come?
   in C++: methods? Ho-hum!

 But always, pretty-please take care,
   that binops have their spaces there.
  
 INSCRUTABLE_MACROS everywhere abound,
   // but in dense code: no comments found.
 Conditions with consequences on one line
   (and so much more, but I've run out of time!)

 The rest of the code may be a muddled mess,
   But always with spaces the binops dress!