🚀 go-pugleaf

In <3144D1F7.E64@axonet.com.au>, Andrew Dalgleish <andrewd@axonet.com.au> writes:
>> And I would assert my code is (1) a lot more PL/1-like and
>> (2) a lot easier to understand.
>
>1. I assume you have #define'd "do" and "end" as "{" and "}".
>How do you encode "do {...} while(...);" ?
>2. The extra semi-colons after each do & end don't achieve anything.
>3. What does "<>" mean in C ?

And I would assert my code is a lot more PL/I like.
>
>Otherwise, this is one example where you can remove goto's without loss 
>of speed and improve clarity.
>This doesn't mean you should never use goto's.

But it was presented as a case where gotos were better.  Sigh.

An assembler maven walked into a bar and asked the bartender: "Do you want
to hear a PL/I programmer joke?"

The bartender was a big fellow with a baseball bat behind the bar which he 
used for crowd control.  "Hey, wait a minute!" the bartender said.  "I am a
PL/I programmer.  And see that fellow over at the pool table?  He's a PL/I
programmer too."  The maven glanced over towards the table and saw a
six-foot-six refugee from the Ohio State offensive line wearing a XXXXL 
tee shirt that was a few sizes too small.  "And check out Fred over by the
juke box, he's a PL/I programmer himself".   The visitor looked over to the
juke box and Fred wearing leathers and had a chain hanging from his belt.

"Now do you still want to tell a PL/I programmer joke?" the bartender asked.

"Naw," the visitor replied.  "I don't want to have to explain it three times."