Yes you should revert back, and I suppose the best solution is to implement the change you were talking about above. How much overhead would it introduce?
/Henrik On Thu, Sep 24, 2009 at 11:45 AM, Alexander Burger <a...@software-lab.de> wr= ote: > Hi Henrik, > >> I'm confused I thought pico didn't do anything else than integers? >> >> In effect if I write (1.2) I would expect to have a dotted pair (1 . >> 2), not something else (If I hadn't seen Tomas' example). > > That's exactly the point. This would be the "clean" solution. But > PicoLisp kind of supports fixedpoint arithmetics. So the dot is a legal > (and necessary) character for the I/O part (for example, in combination > with the '*Scl' global). > > > A possible different "correct" solution would be to allow the dot only > in numbers, but not in symbols. But this would imply an even greater > change to the reader, because currently an atom is first read as a > symbol, and then changed to a number if it looks like one. But perhaps I > should do that? And revert the dot to a pure meta-character? > > > BTW, today I already had a crash at a customer's site, after I installed > the new version. The reason was a mistype: > > =A0 (dm (url> .+User) () > =A0 =A0 =A0(and (may Stammdaten) (list "@usrStamm" '*ID This)) ) > > Note the missing space between '.' and '+User' :-( > > Cheers, > - Alex > -- > UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=3dunsubscribe > -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
