Re: optional argument for function / procedure

I've add a ticket for this request: NCL-1678.

At first glance, it looks like what you mean by the "load" command, but I see that you are talking about something cleaner.

For the next release of NCL, we plan to have gsn_code.ncl, gsn_csm.ncl, contributed.ncl, etc all loaded automatically.

The "import" function that you linked to below is pretty impressive.

--Mary

On Mar 4, 2013, at 7:40 PM, Yagnesh Raghava Yakkala wrote:

>
> Hello Mary,
>
> On Mar 05 2013, Mary Haley <haley@ucar.edu> wrote:
>
>> Hi folks,
>>
>> This has been on our list of things to do for awhile (ticket #NCL-290), but
>> it's not a trivial feature to add.
>>
>> I will add your emails to the ticket to help support its popularity. :-)
>
> Thanks for that,
>
> If I am allowed to request, would it also be possible to implement an
> "import"¹ function and NCLPATH variable package path.?
>
> I am aware of NCL_DEF_SCRIPTS_DIR var which is rather restrictive
> (http://www.ncl.ucar.edu/Document/Manuals/Ref_Manual/NclDefaultScript.shtml ).
> But I believe that having an import function at core would encourage new third
> party packages.
>
> Thanks.,
>
> ¹ There is https://github.com/shanxl/NCL-import written by shanxl , after
> using it a little I felt such a function should come ncl distribution.
>
> --
> ఎందరో మహానుభావులు అందరికి వందనములు.
> YYR
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Thu Mar 7 08:09:27 2013