Alan Manuel Gloria:
> srfi-editors hasn't seemed to reply yet (have they?) so it's probably
> better to assume for now that it's so weird, SRFI won't touch it ^^;

I've gotten a private reply.  The problem isn't weirdness, the problem is that 
the SRFI editors are really busy.  They're within their normal timelines, 
actually; I'm just impatient :-).

Anyway, I don't know of any strong reason to hold back for a long time. These 
*are* changes to the semantics, but they're minor tweaks to previously-unused 
constructs.

Since my last post, I've updated the neoteric-read for Common Lisp, it now 
translates f{} to (f) as well in the "develop" branch.  I've already 
experimented with this in Scheme; I've now done the same in Common Lisp.  Works 
great.  I prefer to test things out in an implementation before we agree to a 
spec change, because there's no point in creating a spec that is not 
implementable (or has a nasty gotcha).  But that's been done.

I've renamed the Common Lisp implementation to "readable.cl", as I had 
threatened earlier, because it now implements more than curly-infix lists.  The 
(neoteric-read) and (enable-neoteric) functions do work for a number of cases.  
The neoteric reader is *not* mature like the Scheme reader is, e.g., the Common 
Lisp implementation cannot currently handle backquote and comma.  This isn't a 
problem with our notation, it's just that implementing these for Common Lisp is 
way more complex than for Scheme.  Steele even gives a public domain 
implementation:
  http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node367.html
but I haven't had the stomach to do it.

Volunteers to implement the Common Lisp backquote/comma in readable.cl would be 
gratefully welcome.

--- David A. Wheeler

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to