Linebreak error-handling

[norihiro-w]

(reported by @laubeg, copied from envinf/ogs5-trunk )

OGS5 is sometimes pretty sensitive to linebreaks in input files at the wrong positions and doesn't provide very meaningfull warnings/errors. There are two examples, where I experienced that:

1. Sourceterm direct conditions

If the file of direct conditions looks like this

8 -0.00005
9 -0.00005

OGS perfectly applies the sourceterms to node 8 & 9. If it looks like this:

8 -0.00005
9 -0.00005

It "terminates normally" but only applied a sourceterm to one of the nodes. There is no warning or error at all. The only difference between the two files is an extra line at the end, which is, in my opinion, a dangerous pitfall because if you're not especially aware of the problem, you probably wont notice it at all.

2. Linebreak before #STOP in *.gli

This file-ending in the *.gli file

#SURFACE
$NAME
rightWall
$POLYLINES
perimeterRight

#STOP

lets OGS wait in this state:

---------------------------------------------
Data input:

forever. The problem is the linebreak before the #STOP. If you changed more than one file before starting the job, it is very hard to find this error. I could not reproduce this error for other input files.