That I don't know. I don't know if you can modify the scanning part of the reader with picolisp, the examples I've seen all work on atoms. You might have to read bytes and process it yourself. Or rewrite the scanner in the C source.
On Sun, Jun 21, 2020 at 3:43 PM Shaughan Lavine <shaug...@nometaphysics.org> wrote: > Thanks for the rapid reply! This is for an android app. I can hardly > require an end user to supply a decimal point. Of course, I can look for > one and supply it if missing. I just wondered if, since this must be a > common use case, there was a better way. > > > Sent from ProtonMail mobile > > > > -------- Original Message -------- > On Jun 21, 2020, 12:16 PM, John Duncan < duncan.j...@gmail.com> wrote: > > > Not a bug, this is the design of the reader (symToNum). Can you make input > include the decimal point? > > On Sun, Jun 21, 2020 at 14:34 Shaughan Lavine <shaug...@nometaphysics.org > <shaughan@nometaphysicsorg>> wrote: > >> Isn't this a bug? >> ------- >> :(scl 2) >> :212 >> 212 >> :212. >> 21200 >> ----- >> Shouldn't 212 be equal to 212. ? >> If not, how do I force a "." after an integer input by a user? Do I >> really have to use a string input and look for a "."? >> >> >> Sent from ProtonMail mobile >> >> >> -- > John Duncan > > -- John Duncan
