note 95711 deleted from language.types.string by danbrown

Note Submitter: ldrut ---- Salil Kothadia on 15-Oct-08 is right about the behavior but not the cause. I don't see it in the docs, but the closing line of a HEREDOC must be identifier, optional semicolon, AND a newline. If the HEREDOC ends the file (EOF immediately follows the closing semicolon of a HEREDOC without an intervening newline), it will give a "Parse error: syntax error, unexpected $end" error. Watch for online editors that automatically strip blank lines from the end of files making the error a bit sneaky. The easiest solution is just to put a comment on a line following the close of the HEREDOC.