🚀 go-pugleaf

      The best bit of code I ever came across ran something like
   the following:
       IF (BOOL) Then
          WRITE(*,*) 'BOOL is True!'
          RETURN
       ENDIF
       IF (.NOT. BOOL) THEN
          WRITE(*,*) 'BOOL is False!'
          RETURN
       ENDIF
       WRITE(*,*) ' See below...'
 
      Well, when I came across this, I decided to keep the general
   structure, but replaced the final WRITE(*,*) Statement with
   a call to our error message handler ERRMSG('Example of Trillian
   Logic'). To the best of my knowledge no customer has ever
   called in about this error message! (I would be real worried if
   one did!)
      In the same set of code, an earlier programmer after a set
   of error conditions reached an error that was ALMOST impossible
   to get. The comment? C User fall down and go BOOM!
   That explained it as well as anything else.
      What through me though one day was looking through a section
   of code and coming across variable names such a LORADO, COWBOY,
   etc. I had no idea where these names came from. Luckily, this
   programmer is a friend of mine. So when I got home, I asked him.
   It was simple, he had the song 'Streets of Lorado' (title?)
   in his head all day, and when he needed a variable name, he took
   it from the song! Between that and his lack of commenting, the
   code was REAL interesting to try to figure out.
 
   Greg_d...@mts.rpi.edu
 
   Disclaimer: Why do I need one? Because my company was bought.
   So these comments do not represent me, my company, or the company
   that bought my company.