It IS the same issue but it has just occurred to me that it is possibly an operator precedence problem. For example my BasicLib library can evaluate an expression like that without requiring the parentheses to force early evaluation of the numeric sub-expression because in it the & operator has a lower precedence than the / operator.
It may be that the compiler uses a different expression evalutor for string rather than numeric expressions which doesn't recognise precedence.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.