Hi Alex!
I think the historical solution, where '.' was a plain meta-character,
was the most consistent one. The dot was simply not allowed within
internal symbols. Tt was only the representation of fixed point numbers
that broke it.
I agree with this :)
--
UNSUBSCRIBE:
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
On Thu, Sep 24, 2009 at 12:04:54PM +0200, Henrik Sarvell wrote:
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?
Perhaps not much overhead, but it needs another quirky rule, like
While
But then you get the kind of break down you referred to earlier?
However for me this is not a problem I've always had space between the
dot and the rest anyway.
On Thu, Sep 24, 2009 at 12:44 PM, Alexander Burger a...@software-lab.de wr=
ote:
On Thu, Sep 24, 2009 at 12:04:54PM +0200, Henrik
On Thu, Sep 24, 2009 at 12:59:33PM +0200, Henrik Sarvell wrote:
But then you get the kind of break down you referred to earlier?
I hope not. It wasn't me who wrote that code ;-)
However for me this is not a problem I've always had space between the
dot and the rest anyway.
Yep, me too.
On Thu, Sep 24, 2009 at 11:20:13AM -0300, TC wrote:
What if instead of modifying the reader itself, a reader macro is implemented?
If '.' is between numbers, fine, if one of the chars next to it is not a
number, split.
In that sense, ' . ' is already some kind of reader macro (more real
