On 09/09/2009 06:09 PM, Brian Harvey wrote:
> Yah, I see how either of the two original proposals falls naturally out of
> simple parsing rules. What I don't see is how it would happen that someone
> who meant foonbar (or, to take a slightly more realistic example,
> the symbol foo(n)bar) would type '|foo(|n|)bar| instead of just '|foo(n)bar|.
> So if the user /does/ type '|foo(|n|)bar| I claim the only plausible
> reading of that /as a communication from a human being/ is that s/he wants
> the symbol foo(|n|)bar, including the vertical bars.
In addition to supporting the package-prefix-case mentioned before
(compound symbol |foo|:|bar| vs simple symbol |foo:bar|) there is
also the use-case case of symbols with either | or \: or both:
\||\|\| => the 3-character symbol (string->symbol "|\\|")
(assuming one has both |-escapes and \-escapes, as in
Common Lisp - and Kawa).
--
--Per Bothner
[email protected] http://per.bothner.com/
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
