[ncl-talk] NCl exit on error

[Marston Ward]

Hi Dennis,

I do this (use begin…end) religiously so that is not the cause in this case (see attached script (work in progress))
It is not big deal only a bit annoying.

/M

Marston S. Ward

On 22 Nov 2017, 17:58 +0100, Dennis Shea <shea at ucar.edu>, wrote:
http://www.ncl.ucar.edu/Document/Manuals/Ref_Manual/NclStatements.shtml#Blocks

Must use

begin
   ...
end

On Wed, Nov 22, 2017 at 8:35 AM, Marston Ward <marston.johnston at gu.se<mailto:marston.johnston at gu.se>> wrote:
Hi,

Is there a way to get NCL to exit on detecting a syntax error in a function and not continuing on in the main program?
As it stands now in NCL 6.4.0, if an error is detected in a function called from the main program, the error is listed in the
terminal output at the beginning of the run but then the script continues.
So in the case of debugging when there are lots of print statements, I have to scroll up to the beginning of the run to
check for errors.

I hope I’m clear about this.

Best,
/M

Marston S. Ward

_______________________________________________
ncl-talk mailing list
ncl-talk at ucar.edu<mailto:ncl-talk at ucar.edu>
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20171122/d421c364/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build_modis_joint_histograms.ncl
Type: application/octet-stream
Size: 6593 bytes
Desc: build_modis_joint_histograms.ncl
URL: <http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20171122/d421c364/attachment.obj>