Using Mark Kantrowitz old but very handy infix we noticed some peculiar pattern of errors where very basic expressions do not correctly convert infix expressions into prefix ones. The version I just tried was this one: http://www.cliki.net/infix
in => pre, red for incorrect
"a + 1" => (+ A 1) "s + 1" => S+1 "s - 1" => S-1 "s * 1" => (* S 1) "a + 1.5" => (+ A 1.5) "s + 1.5" => (+ S 1.5) "s + s" => (+ S S) "s + 1 + 1" => (+ S+1 1) "s + 1e1" => (+ S 10.0)
Can somebody see a pattern here? AFAIK, the combination of the one letter variables names that are characters D, E, F, L, or S followed by "+" or "-" and then followed by an int does not work.
Is this a bug or some very special case that is supposed to work like this for no (to me) obvious reason? If this is bug, how could this have slipped through the net for so many years? I know many people have using this software. I tried various versions of infix.lisp. Are D, E, F, L, or S special tokens? If so, what do they mean, and where are they declared?
Confused, Alex
---- test program spitting out the variable names not working ------
This should print nothing:
(map nil #'(lambda (Char) (when (symbolp (read-from-string (format nil "#i(~A + 1)" Char))) ;; should be a list, NOT a symbol! (print Char))) "ABCDEFGHIJKLMNOPQRSTUVWXYZ")
but prints:
#\D #\E #\F #\L #\S
Prof. Alexander Repenning
University of Colorado Computer Science Department Boulder, CO 80309-430
vCard: http://www.cs.colorado.edu/~ralex/AlexanderRepenning.vcf
On Fri, Dec 2, 2011 at 8:56 PM, Alexander Repenning ralex@cs.colorado.edu wrote:
Using Mark Kantrowitz old but very handy infix we noticed some peculiar pattern of errors where very basic expressions do not correctly convert infix expressions into prefix ones. The version I just tried was this one: http://www.cliki.net/infix
in => pre, red for incorrect
"a + 1" => (+ A 1) "s + 1" => S+1 "s - 1" => S-1 "s * 1" => (* S 1) "a + 1.5" => (+ A 1.5) "s + 1.5" => (+ S 1.5) "s + s" => (+ S S) "s + 1 + 1" => (+ S+1 1) "s + 1e1" => (+ S 10.0)
Can somebody see a pattern here? AFAIK, the combination of the one letter variables names that are characters D, E, F, L, or S followed by "+" or "-" and then followed by an int does not work.
Didn't look into the code, but those letters are special…
CL-USER 15 > (list 1.0d+0 1.0d-0 1.0e+10 1.0e-10 1.0f+0 1.0f-0 1.0l+0 1.0f-0 1.0s+0 1.0s-0) (1.0D0 1.0D0 1.0E10 1.0E-10 1.0 1.0 1.0D0 1.0 1.0S0 1.0S0)
//JT
On Dec 2, 2011, at 7:08 PM, Joshua TAYLOR wrote:
On Fri, Dec 2, 2011 at 8:56 PM, Alexander Repenning ralex@cs.colorado.edu wrote:
Using Mark Kantrowitz old but very handy infix we noticed some peculiar pattern of errors where very basic expressions do not correctly convert infix expressions into prefix ones. The version I just tried was this one: http://www.cliki.net/infix
in => pre, red for incorrect
"a + 1" => (+ A 1) "s + 1" => S+1 "s - 1" => S-1 "s * 1" => (* S 1) "a + 1.5" => (+ A 1.5) "s + 1.5" => (+ S 1.5) "s + s" => (+ S S) "s + 1 + 1" => (+ S+1 1) "s + 1e1" => (+ S 10.0)
Can somebody see a pattern here? AFAIK, the combination of the one letter variables names that are characters D, E, F, L, or S followed by "+" or "-" and then followed by an int does not work.
Didn't look into the code, but those letters are special…
CL-USER 15 > (list 1.0d+0 1.0d-0 1.0e+10 1.0e-10 1.0f+0 1.0f-0 1.0l+0 1.0f-0 1.0s+0 1.0s-0) (1.0D0 1.0D0 1.0E10 1.0E-10 1.0 1.0 1.0D0 1.0 1.0S0 1.0S0)
//JT
-- Joshua Taylor, http://www.cs.rpi.edu/~tayloj/
Nice!
Yes, it does appear to be a genuine bug which confuses simple expressions such as "e + 1" with floating point literals. Bad floating point literal parsing going on here:
1) floating point numbers representations require the exponent marker to be preceded by at least a digit 2) do not allow spaces between the exponent marker, the exponent sign and exponent digits.
I found this function in infix.lisp which appears to be the culprit:
(defun fancy-number-format-p (left operator stream) (when (and (symbolp left) (find operator '(+ -) :test #'same-operator-p)) (let* ((name (symbol-name left)) (length (length name))) (when (and (valid-numberp (subseq name 0 (1- length))) ;; Exponent, Single, Double, Float, or Long (find (subseq name (1- length)) '("e" "s" "d" "f" "l") :test #'string-equal)) (read-token stream) (let ((right (peek-token stream))) (cond ((integerp right) ;; it is one of the fancy numbers, so return it (read-token stream) (let ((*readtable* *normal-readtable*)) (read-from-string (format nil "~A~A~A" left operator right)))) (t ;; it isn't one of the fancy numbers, so unread the token (push operator *peeked-token*) ;; and return nil nil)))))))
Just making it return nil will fix the conversation of expression such a "e + 1" to be (+ e 1) but of course will also ruin the capability to recognize real float literals. Does anybody have the energy to fix this? Time to go to bed...
Still surprised this bug has not surfaced before.
Alex
Prof. Alexander Repenning
University of Colorado Computer Science Department Boulder, CO 80309-430
vCard: http://www.cs.colorado.edu/~ralex/AlexanderRepenning.vcf
-
Alexander Repenning -
Joshua TAYLOR -
Steve Haflich