topic Re: %str(ERR)OR in SAS Programming

%str(ERR)OR

wzl9527 — Mon, 28 Feb 2022 02:47:47 GMT

While I review other's program,see code like this '%str(ERR)OR','%str(WARN)ING',why programming like this other than "%str(ERROR)",%strWARNING

Re: %str(ERR)OR

wzl9527 — Mon, 28 Feb 2022 02:49:47 GMT

my fault,it's '%str(warning)'

Re: %str(ERR)OR

Tom — Mon, 28 Feb 2022 03:13:11 GMT

Because they are using lazy log scanning tools that cannot tell the difference between the text ERROR in the code and an actual ERROR message generate by that code (or by SAS itself). By adding the extra macrro quoting (which is NOT needed) then the code no longer has the text ERROR as there is a ) in the middle of it. Using %STR(ERROR) would defeat that purpose.

Personally I use this grep string to search for ERROR messages and I do not get false positives from code lines echoed in the log.

grep '^ERROR.*:' myfile.log

Re: %str(ERR)OR

wzl9527 — Mon, 28 Feb 2022 06:14:20 GMT

thank you!

Re: %str(ERR)OR

AllanBowe — Tue, 01 Mar 2022 11:11:52 GMT

This is a convention we use in the SASjs Core library quite extensively.

This library was built to support lazy programmers, and sometimes the fastest way to search for an error in a log (especially within applications that do not support regex by default, such as a browser) is simply to CTRL+F and type "ERROR".

By breaking up the word ERROR into %str(ERR)OR, the number of false positives are drastically reduced. That is the only reason.

Re: %str(ERR)OR

wzl9527 — Fri, 04 Mar 2022 08:11:11 GMT

Thanks！