-=> Jagossel wrote to Deavmi <=-
Ja> Same thing with SQL Server and SQL Scrpits or stored procedures.
Ja> Error on line 73...
Ja> "How exactly does a blank line cause an error? This isn't BrainF***!"
Ja> I susoect it has a lot of how the scripts gets parsed in regards to
Ja> line numbers; not really sure how to get to the right line with the
Ja> given line number.
I would say it's because the parser has to be sure there is an error and that
it doesn't prematurely flag an error inside a long block (like a function or
loop), so quite often, the offending error is well before where the compiler or
interpreter flags it. For example, nest a few if-then-else statements in a
bash shell script and leave out an inner "fi", and depending on the code, the
error can be indicated a fair way down the script. Similar things happen when
quotes aren't closed, sometimes these will go all the way to the end of the
file with "unexpected end of file".
... I can see clearly now, my brain is gone...
--- MultiMail/Win32 v0.49
■ Synchronet ■ Freeway BBS in Bendigo, Australia.
|
