Re: NCL 6.2.0, Bug in str_match_ind?

Robert,

The intention of str_match_ind is to do string literal comparison.
In 6.1.2, we used Regex to do the work, which caused some issues,
and in 6.2.0, we moved to literal string compare functions.

For the above reason, in 6.1.2, str_match_ind worked (not intentional) with regular expression,
but not in 6.2.0. So far, there is no new functions for regular string expressions.

There is a discussion here within the NCL team about if we need another function
for string regular expressions, but there is no conclusions reached.

We certainly welcome users to weigh in on this issue.

Regards,

Wei
On Apr 7, 2014, at 9:06 AM, Robert Schuster <rxschuster@gmail.com> wrote:

> Dear NCL team,
>
> str_match_ind seems to have lost it’s capability to match regular expressions. Try this example:
>
> test = (/"wkWidth","mpCenterLatF“/)
> print(str_match_ind(test,"^mp[a-zA-Z]*“))
>
> in NCL version 6.1.2 the result was 1, in version 6.2.0 the result is a missing value (-2147483647).
>
> Is there a maybe a new function which is able to match regular expressions?
>
> Thanks in advance!
> Robert
> _______________________________________________
> 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 Mon Apr 07 10:51:41 2014