O> On Mon, Sep 25, 2017 at 10:19 AM, Brandon Allbery <allber...@gmail.com
<mailto:allber...@gmail.com>> wrote:On Mon, Sep 25, 2017 at 3:09 AM, Julien Simonet <kernel.jul...@gmail.com <mailto:kernel.jul...@gmail.com>> wrote: I think your problem is coming from a (") missing at line 3. At the same line, the semicolon (;) is misplaced : it should be at the end if line. It took older perl over a decade to come up with better error messages for this. Can we please do it a bit sooner?
On 09/25/2017 07:25 AM, Brandon Allbery wrote:
So as to make this not entirely content-free: I would suggest that the string language note the line on which it sees a bare newline, and if it subsequently hits a syntax error while still parsing that string it could output something like perl 5's "Possible runaway multi-line string starting on line ..." as a suggestion.
Usually, when I get an error message, I go straight to the error line to see if I can figure it out myself. Sort of a brain game. If I can't figure it out on my own, then I read the error message. If the error messages makes no sense, like the one I saw here -- "Variable '$IAmFrom' is not declared " when it actually was -- then I go the last line I actually worked on and work backwards until I find what I forget or booboo'ed. It can be miserable to find a missing quote or curly bracket. Geary color codes things pretty well, but not so much on the curly brackets: it will show you the matching opening bracket in a dark blue that is pretty hard to tell apart from the native black. (I use Geany as it works over "ssh -X" really well.) If I have missed a quote, sometimes the error message is hundreds of line below the booboo and a lot of times at the end of the file. And sometimes I just need an extra pair of eyes. Thank you guys! :-) -T
