Hi All

I am trying to tokenize &Temp using '.'

To say , since that &Temp is not having '.' in it , &Temp should not get tokenized when the following STRTOK is applied.

-SET &Temp = 'ABCD*E *TR &|FGH TR ABOUT TR';
-SET &TL = &Temp.LENGTH;
-SET &REP = '.';

-SET &MODSTR = GETTOK(&Temp,&TL,1,&REP,50, 'A50');
-SET &MODSTR = TRUNCATE(&MODSTR);

-TYPE &Temp;
-TYPE &MODSTR;


o/p

ABCD*E *TR &FGH TR ABOUT TR;
ABCD*E;

It gets corrected when STRTOK is rewritten as

-SET &MODSTR = GETTOK(&Temp,&TL,1,&REP.EVAL,50, 'A50');

I dont understand why , Can anyone help me out ? What is the significance of EVAL here ?

This message has been edited. Last edited by: Kerry,

Navin,

Could be a specific thing for the 71 release that you're working with.
I tried your code in 76(2) and there it just gives me the correct output.
Maybe upgrade is in order?

The .EVAL forces an evaluation of the variable string prior to the parsing of the DM statement that contains the variable.

No doubt J.G. will be along any moment with an IB explanation?

T

Also,


-SET &REP = '-';

-IF (&REP EQ '.') THEN REPO ELSE NOREPO;
-REPO
-TYPE WORKS SUCCESSFULLY
-NOREPO

'-'(hiphen) and '+' equates to '.' in the above code. Others doesnot work obviously. Any idea why ?

Dialog Manager attempts to treat comparisons as numeric-to-numeric. The values '.', '-', '+', '0', and ' ' are treated as representations of zero, and are therefore all 'equal'.

(I guess someone once authored validation/classification/parsing code to handle a potential number, and allowed for the digits, signs, decimal points and leading spaces. Once all the individual characters pass that test, evaluation of the "number" begins with zero and swallows the characters one at a time. Nothing happens to change the initial value, so zero it is....)

ASIS(&var) will force &var to be treated as a character string.

This message has been edited. Last edited by: j.gross,

Thanks Gross
that worked.