David A. Wheeler scripsit:

> In systems that implement SRFI-88, a sequence of text ending in ":" is a
> keyword and NOT a symbol.  Interestingly enough, there's an exception -
> a ":" by itself continues to be a symbol.  It appears that there are
> 5 Scheme implementations that implement SRFI-88

To wit, Chicken, Guile, Kawa, STklos, Scheme 7.  Guile 2.0 only supports
the safe #:foo format, at least by default.  Chicken and Kawa support
the #:foo and foo: formats, but not the Common Lisp :foo format, which
produces identifiers, again by default.  Scheme 7 supports all three
formats.  STklos supports foo: and :foo but not #:foo, and furthermore
treats : as a keyword too.

> So it seems that ":" *could* be used for SUBLIST in Scheme.  I still
> worry about problems using it with other Lisps.

It could, but it is a standard identifier, and as you say, single-symbol
ASCII identifiers that aren't already in use are rather rare.

> The data we have so far suggests to me that "$" is slightly better than
> ":".  The ":" is used more than "$" as an operator in Emacs Lisp, and
> "$" is the standard name in Haskell.  But it's no slam-dunk case.
> Are there other reasons (or amplifications of them) to prefer "$",
> ":", or some other sequence of characters?

Perhaps "$$" would be better, and would certainly fit well with "\\".
But I am not proposing it at this stage.

-- 
All Gaul is divided into three parts: the part          John Cowan
that cooks with lard and goose fat, the part            http://ccil.org/~cowan
that cooks with olive oil, and the part that            co...@ccil.org
cooks with butter. --David Chessler

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to