Modified the description so it aligns a bit better with the test cases. Sadly, I can't change the test cases to make sense without invalidating 447 solutions.

• Why do you prefer minimalist code and not an OOP boilerplate? (And why that would be an issue?)
• By test driver you mean the example test code?
• The Kata doesn't use random for spacing please read the description again.
• If you want text abbreviated please make a new comment and tag it as suggestion to polish on it's own discussion thread.

What do you not understand?

The macro was an ugly hack I did mostly due to being upset about the Javaisms of this Kata. I realize now it could have been done better by forwarding the call to my function in a Carboat class, or importing my function to a Carboat namespace.

Also, you don't actually need using namespace std; to pass.

When I submitted this solution it would come back with compile error if I didn't include that line. The hidden full test suite needed it. The "quick check" tests already included it, so it wasn't that.

language...?