I previously said: > The big step "to be done" is to support #'name, which is Common Lisp's > (function name) but is Scheme's (syntax ...). So I need a new library > interface to let it know that a "Common Lisp" mode is enabled, so that it > will return (function ....) instead.
That's done now... so we have basic support for Common Lisp. An "unsweeten -C" can handle #'name as (function name), as well as a few other Common Lisp constructs like "#:" and "#." when "-C" is invoked. That's on top of ` and , and ,@. There's more that can be done, in particular, it'd be best if sweeten could do a better job reading Common Lisp. It's overall a half-hearted job for Common Lisp, but fully supporting Common Lisp would probably be best done by re-implementing it in Common Lisp (probably doing a mass hook into its readtable). That said, we could do much more, but it'd be best to hear from actual users to see what their issues are. If anybody tries this out with Common Lisp, please speak up!! --- David A. Wheeler ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss