It's the same with 'f', i.e. 1f+1 gives 10 and 1f + 1 an error (if f is not defined, else a different result again). And if someone introduces 'g' for "engineering notation", there will be an exception for this letter, too.
By the way, has the bug x = 10; x.1 returning 1.0 been handled in 0.4? It's still there in 0.3. On Monday, January 5, 2015 2:32:00 PM UTC+1, Simon Byrne wrote: > > * julia> 3e+1* >> * 30.0* >> >> *julia> 3e + 1* >> >> * 9.154845485377136* >> > > Perhaps this is a good reason to change behaviour such that e is no longer > a constant: it has always seemed bit odd to use a valuable latin singleton > in this way. We could use a unicode script e (U+212F) instead, as suggested > by wikipedia: > > http://en.wikipedia.org/wiki/Numerals_in_Unicode#Characters_for_mathematical_constants > > s >
