BRAINscript changes - Data360_Analyze - Latest

The unless operator is no longer supported; instead, you can use if then else to achieve the same results.

For example:

errorRatio = badResultsCount / totalCountunlesstotalCount == 0then0

This script would now be written using if then else, as follows:

if totalCount == 0thenerrorRatio = 0else errorRatio = badResultsCount / totalCount

Emit/exclude wildcard now fails if you use u", r", ur", ru" style strings. Previously, using these strings would produce incorrect results. This affects emit and exclude statements in the following formats:

• emit wildcard u"<someString>"
• emit wildcard r"<someString>"
• emit wildcard ur"<someString>"
• emit wildcard ru"<someString>"
• exclude wildcard u"<someString>"
• exclude wildcard r"<someString>"
• exclude wildcard ur"<someString>"
• exclude wildcard ru"<someString>"

Emit wildcard with \x, \u style escapes now correctly passes these through to expert where they are evaluated correctly. Previously, the backslash character was stripped when sending to expert, so \x10 rather than matching the newline (\n) character would match the literal string "10".

Previously, the following two examples would output the value of x under the column name y:

x=3emit x as y

x=3y=2emit x as y

Now, the second example would fail because y has been defined as a variable. The first example would still work because y has not been declared as a variable, so the column name is output as the literal value of "y".

Statements such as a==b will now error if they are used as a top level statement. However, it is possible to use this type of statement in a comparison context, for example:

if (a==b) thendo something

The first parameter of an evalIf statement can be either a boolean literal, or a boolean expression, for example, "or", "not", "and", parenthesis "(",")" logical operators are allowed, as are the "==" and "!=" comparators.

If you want to use the comma-notation (',') within emit, exclude, or rename statements in the context of an evalIf, the evalIf argument within which it is used must be wrapped in curly braces {}

For example:

evalIf(true, {emit "foo" as "Bar"}, {emit "barry" as "mary"})