Inconsistent Result Cases

armsys · Post by **armsys** » Tue Jun 11, 2013 1:57 am

First of all, Macro Scheduler's logical comparision is case sensitive.
ie, in MS, "yes" is not equal to "YES".
You can test it:

Code: Select all

Let>result={ "yes" = "Yes" }
MDL>result

Nonetheless, the true/false results generated by commands are not always consistent in terms of Upper/Lower/Capital cases.
For example, WW_Result yield upper case TRUE or FALSE.
On the other hand, ProcessExists> will generate True or False.
Marcus, would you standardize all logical results to be the same case-- either Upper, Lower, Capital case?
Thanks.

CyberCitizen · Post by **CyberCitizen** » Tue Jun 11, 2013 3:12 am

Or Not Case Sensitive. But Yes, This Has Caught Me Out Once Or Twice.

armsys · Post by **armsys** » Tue Jun 11, 2013 3:26 am

Hi CyberCitizen,

CyberCitizen wrote:Or Not Case Sensitive. But Yes, This Has Caught Me Out Once Or Twice.

Your crytic semantic poem torments my brain. Is this a Hobbit or Vulcan language? Sorry, what exactly do you mean in plain English?

CyberCitizen · Post by **CyberCitizen** » Tue Jun 11, 2013 3:34 am

Instead of it having to be an exact match eg Must be YES or Yes it is not case sensitive so if it searching for results it doesn't matter if its written as YES, Yes, yes, yEs. Etc. As long as the information contained in that variable = those 3x letters YES it doesn't matter how its written.

That being said it would be easier to have it all uppercase or lowercase.

armsys · Post by **armsys** » Tue Jun 11, 2013 3:47 am

Hi CyberCitizen,

CyberCitizen wrote:Instead of it having to be an exact match eg Must be YES or Yes it is not case sensitive so if it searching for results it doesn't matter if its written as YES, Yes, yes, yEs. Etc. As long as the information contained in that variable = those 3x letters YES it doesn't matter how its written.

Rather unfortunately, for example, WW_RESULT returns TRUE or FALSE-not exactly "3x letters".