Re: "e" not to be for exponentiation

[Timur Safin]

This is not exactly match that they said. It would rather be $zu function returning the 
old behavior if it is needed. Here is this recent CDS587 excerption:

<CDS587>
BRIEF DESCRIPTION: Provide switch so exponent must be upper case 'E'
EXTERNAL DOCUMENTATION:
Since Release 4.1, Cache' has allowed the exponent designator for a number
in scientific notation to be either upper or lower case, 'E' or 'e'.
However, this is not compatible with some programs written in other dialects
of the M language, which recognize only upper case 'E'.  Those programs use
lower case 'e' as a string delimiter.  This change provides a switch which
restores the behavior of recognizing only upper case 'E' as the exponent
designator.  The default behavior will continue to allow lower case 'e'.
...
</CDS587>
Timur
On 20.07.2004 9:23, Denver Braughler said the following:
In comp.lang.mumps message <[EMAIL PROTECTED]>, 
George Timson wrote:

... [The USA Veteran Affairs Department] has gotten word from 
InterSystems that the lowercase-e 'enhancement' will be backed
out of future Cache' releases.

Basically this means that X=+$P($E(X,1,15),"E") will never result in an error.
This is in accordance with what was standard MUMPS.
I believe that there is no harm in lowercase "e" in numlits.
So if ISC has done this correctly, the COS constant 123e4 should 
continue to be legal.  
But +"123e4" will evaluate to 123 instead of 1230000.