I'm using a 3rd party JSON API that for some reason returns floatingpoint numbers in the form "0E-8" rather than just "0" or "0.0". Theleading zero is actually valid according to the JSON spec, but failswith the new kdb+ 3.3 parser:q).j.k"[1E-8]",1e-08q).j.k"[0E-8]"'illegal char E at 2Josh
