Description David Williams 2012-03-26 04:02:12 EDT

note to self ... there's a few places in build scripts similar to 

cat >>$buildResults/compilelogs.html <<EOF
<tr><td><a href="$f">$PA_FN - $FN</a></td></tr>
EOF

Where the <<EOF
....
EOF

is used. 

It is pretty handy, but, I've found it sensitive to formatting. The closing EOF has to start in the very first column (I guess be proceeded by and EOL) and once when doing some "automatice" formatting, correcting indentations, some of them were "move over" to align with their associated code, when then lead to some hard to track down errors (similar to when a quote is missing and hundreds of lines later you get an "unexpected end of file found". (reminds of the very first fortran compiler I used ... if there was a compile error, the only message you got was "a compiler error occurred" :) 

At any rate ... code that's sensitive to formatting is kind of fragile (especially for new comers who don't often use this "block input" construct often ... so, would be nice to find another way to do the same thing, not so fragile to formatting.