Re: Precedence for reader extensions

[Mikael Djurfeldt <mikael@djurfeldt.com>]

On Tue, Feb 19, 2013 at 5:42 PM, Mikael Djurfeldt <mikael@djurfeldt.com> wrote:
> * The suggested change *does* make things conceptually simpler and
> more flexible (= you can always override hash syntax if you want;
> compared to the current: you can override #| but not other hash
> syntax)

Just to try to be clear:

What I write above is not strictly true.  The current Guile *already*
allows you to override standard syntax, even without my changes.  What
my changes do is to cleanup the old mechanism so that it doesn't fail
when whitespace is involved.

An example of how it currently fails is that you *can* override when
you spell quote using single quote ("'OBJECT") since no whitespace is
involved while you cannot override when you spell quote using the
symbol quote ("(quote OBJECT)") since there's whitespace to be
swallowed before the OBJECT.

I do respect the attitude that the user shouldn't be able to override
standard syntax, even though I don't think it matters much given the
state of the current mess.  But I think you agree that we either need
to apply my fix (making the current overriding mechanism useful) or
fix scm_read_sharp so that it conforms with the behavior of flush_ws.