<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Coming back to this very briefly. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I use ncl interactively a lot of the time while writing scripts. If there was a way to indicate that one was within a blocked comment I think it would be useful. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Currently I occasionally get stuck in nested do/if statements with no indication as to what level I'm at. Block comments add another potential level of confusion. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">My initial thought would be to change the prompt when inside a block comment as below. </div><div class="gmail_default"><p style="font-family:Menlo;margin:0px;font-size:11px">ncl 1></p><p style="font-family:Menlo;margin:0px;font-size:11px"><span style="font-family:verdana,sans-serif;font-size:small">to</span> </p><p style="font-family:Menlo;margin:0px;font-size:11px">ncl 1;</p><p style="font-family:Menlo;margin:0px;font-size:11px"><br></p><p style="font-family:Menlo;margin:0px;font-size:11px"><br></p><p style="font-family:Menlo;margin:0px;font-size:11px"><br></p><p style="margin:0px"><span style="font-family:verdana,sans-serif;font-size:small">Alan. </span><br></p><p style="font-family:Menlo;margin:0px;font-size:11px"><span style="font-family:verdana,sans-serif;font-size:small"><br></span></p><p style="font-family:Menlo;margin:0px;font-size:11px"><span style="font-family:verdana,sans-serif;font-size:small"><br></span></p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 6:53 PM, Maria Gehne - NOAA Affiliate <span dir="ltr"><<a href="mailto:maria.gehne@noaa.gov" target="_blank">maria.gehne@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, the more forgiving to forgetfulness the better.<span class="HOEnZb"><font color="#888888"><div><br></div><div>Maria</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 4:42 PM, Dennis Shea <span dir="ltr"><<a href="mailto:shea@ucar.edu" target="_blank">shea@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Je suis d'accord ... D<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 3:44 PM, David Brown <span dir="ltr"><<a href="mailto:dbrown@ucar.edu" target="_blank">dbrown@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Wed, Jul 1, 2015 at 3:13 PM, Alan Brammer <<a href="mailto:abrammer@albany.edu" target="_blank">abrammer@albany.edu</a>> wrote:<br>
> Hi all,<br>
><br>
> My vote would have to be on the /; ;/ notation for consistency with<br>
> existing comments.<br>
><br>
> This would also hopefully mean you can leave the trailing ;/ when you<br>
> uncomment a block. I know I would end up with a ton of trailing */ which<br>
> would then trip errors otherwise.<br>
><br>
</span>That's an interesting observation, and in my mind adds points in favor<br>
of the /; ;/ syntax.<br>
-dave<br>
<div><div><br>
><br>
> Alan.<br>
><br>
><br>
><br>
> On Wed, Jul 1, 2015 at 2:42 PM, Karin Meier-Fleischer<br>
> <<a href="mailto:meier-fleischer@dkrz.de" target="_blank">meier-fleischer@dkrz.de</a>> wrote:<br>
>><br>
>> Hi to all,<br>
>><br>
>> thanks to Mary for the welcome note, too. :-)<br>
>><br>
>> I would prefer /* .. */ as used for C/C++.<br>
>><br>
>> The /; .. ;/ looks a little bit strange and in my opinion the /* .. */ is<br>
>> much better to identify in scripts.<br>
>> But that’s just my view.<br>
>><br>
>> Bye,<br>
>> Karin<br>
>><br>
>><br>
>><br>
>> Am 01.07.2015 um 17:28 schrieb Rick Brownrigg <<a href="mailto:brownrig@ucar.edu" target="_blank">brownrig@ucar.edu</a>>:<br>
>><br>
>> Greetings everyone,<br>
>><br>
>> Thanks to Mary for the welcoming introductory note. We do have a minor<br>
>> feature in the works for NCL as a language, but one which I think many will<br>
>> find convenient: block-comments, whereby one can readily comment out<br>
>> multiple lines at once.<br>
>><br>
>> The question to the group is: what should that look like?<br>
>><br>
>> As a C/C++/Java programmer, my natural inclination would be /* ... */<br>
>> style bracketing comments. However, I personally think that notation looks<br>
>> out of place in NCL code. Given NCL's Fortran influences, we could turn to<br>
>> that language -- I'm surprised however that modern Fortran does not have a<br>
>> block-comment (?)<br>
>><br>
>> With ";" being NCL's line-comment character, one suggestion that has stuck<br>
>> is<br>
>><br>
>> /; ... ;/ bracketing notation.<br>
>><br>
>> To those of you who might not be C/C++/Java programmers, is there another<br>
>> more natural style appropriate for a language like NCL?<br>
>><br>
>> We appreciate any comments...<br>
>><br>
>> Rick<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> nclpy-group mailing list<br>
>> <a href="mailto:nclpy-group@ucar.edu" target="_blank">nclpy-group@ucar.edu</a><br>
>> List instructions, subscriber options, unsubscribe:<br>
>> <a href="http://mailman.ucar.edu/mailman/listinfo/nclpy-group" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/nclpy-group</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> nclpy-group mailing list<br>
> <a href="mailto:nclpy-group@ucar.edu" target="_blank">nclpy-group@ucar.edu</a><br>
> List instructions, subscriber options, unsubscribe:<br>
> <a href="http://mailman.ucar.edu/mailman/listinfo/nclpy-group" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/nclpy-group</a><br>
><br>
_______________________________________________<br>
nclpy-group mailing list<br>
<a href="mailto:nclpy-group@ucar.edu" target="_blank">nclpy-group@ucar.edu</a><br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/nclpy-group" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/nclpy-group</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
nclpy-group mailing list<br>
<a href="mailto:nclpy-group@ucar.edu" target="_blank">nclpy-group@ucar.edu</a><br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/nclpy-group" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/nclpy-group</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
nclpy-group mailing list<br>
<a href="mailto:nclpy-group@ucar.edu">nclpy-group@ucar.edu</a><br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/nclpy-group" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/nclpy-group</a><br>
<br></blockquote></div><br></div>