Page 1 of 1
bug of newLISP v.10.6.0
Posted: Sat Jan 24, 2015 2:30 am
by Jian Leng
Hi NewLisper,
I found the predicate number? has a bug.
when input number? 2323abc, it will return
true. So I think its a bug.
David
Re: bug of newLISP v.10.6.0
Posted: Sat Jan 24, 2015 3:47 am
by rickyboy
It's not a bug. 2323 is a number.
Re: bug of newLISP v.10.6.0
Posted: Sat Jan 24, 2015 3:57 am
by rickyboy
:)
The TLDR is that newlisp parses 2323abc as two atoms, namely the integer 2323 and the symbol abc. Finally, the primitive number? only reads its first argument (and ignores any additional arguments). So saying
is the same as saying
Re: bug of newLISP v.10.6.0
Posted: Sat Jan 24, 2015 5:14 am
by Jian Leng
I see. Thanks a lot.
David
Re: bug of newLISP v.10.6.0
Posted: Sat Jan 24, 2015 8:24 am
by xytroxon
That is not always a good "feature"...
Code: Select all
> (setq abc 123OX 456)
456
> abc
123 ; abc should be 1230
> X
nil ; X should be 456
In the dyslexic process of anticipating to shift to type the "X" key, I hit the "O" (oh) key instead of the "0" (zero) key. (aka "toushie" typing ;o) Parser missed an error it might/should have caught by enforcing whitespace separation at the end of a numerical value.
-- xytroxon
Re: bug of newLISP v.10.6.0
Posted: Sun Jan 25, 2015 2:53 pm
by Lutz
The way newLISP parses numbers is practical when parsing normal text. Numbers are often followed by unit identifiers, e.g.:
Code: Select all
> (parse "length 100cm")
("length" "100" "cm")
> (parse "temperature is 100°")
("temperature" "is" "100" "°")
> (parse "weight is 10lbs")
("weight" "is" "10" "lbs")
> (parse "100$")
("100" "$")
> (parse "100¥")
("100" "¥")
> (parse "100€")
("100" "€")
> (parse "100e3€")
("100e3" "€")
> 100e3
100000
Re: bug of newLISP v.10.6.0
Posted: Mon Jan 26, 2015 7:48 am
by xytroxon
Please add a few of those examples to the
parse section of the newLISP manual.
We humans are not well-versed in these advanced logic designs of the Krell*...
-- xytroxon
*
http://en.wikipedia.org/wiki/Krell