Re: reading symbols containing apostrophe

[Tom Gillespie]

Hi Taylan,
    Thank you for the explanation. Replies in line. Best!
Tom

> It's quite common for implementations to extend the standard, so
> something that's "an error" in the standard might be allowed in an
> implementation.

In this instance I think the situation is worse than if the standard
said this was an error. In fact the standard doesn't say this is an
error at all, which would be better than the current situation.
Where nearly all other implementations will read 'a'b'c as three
separate symbols, Guile reads it as a single symbol, silently
diverging from the standard without warning (until something
comes crashing down as a result of the difference later).

> This is evidently one of those cases.

Unfortunate that it does not seem to be documented anywhere.
Would it make sense to bring this up on the dev mailing list and
submit a patch to the documentation to indicate where guile is
incompatible with the standard?

> I would not *rely* on Guile supporting this either though.  Maybe in a
> future version the reader will be changed and it will stop working.

For now I will mark it as a quirk that will have to be tracked.