Re: [Readable-discuss] Readable version 1.0.2 released!
Readable Lisp/S-expressions with infix, functions, and indentation
Brought to you by:
dwheeler
From: David A. W. <dwh...@dw...> - 2014-06-25 00:51:25
|
Drat. What do you suggest? On June 24, 2014 5:28:39 PM EDT, Alan Manuel Gloria <alm...@gm...> wrote: >On Mon, Jun 23, 2014 at 3:41 AM, David A. Wheeler ><dwh...@dw...> wrote: >> Version 1.0.2 of the "readable" package is now available!! >> >> It's a collection of small tweaks and improvements, primarily in the >documentation and Scheme implementation. Having many small >improvements is a *good* thing. In particular, there are no >incompatible interface/language changes; I view avoiding incompatible >language changes as critically important. >> >> Below is the ChangeLog entry for this version, which describes the >highlights. If you want more detail, "git log -p" will tell all. >> >> --- David A. Wheeler >> >> >> ChangeLog for version 1.0.2: >> * Various minor Scheme bug fixes, e.g., improve EOF handling >during >> symbol reading, fix detection of unsupported #. >> * Many portability improvements, especially for Chicken >Scheme and >> rscheme. E.G., remove all "#:" in source, >> change "throw" to "raise", rename internal "body" to >"read-body". >> Modify sweet-run so it works unchanged on Mac OS Darwin. >> * Many changes to eliminate warnings in various Schemes, >e.g., >> change (cond .. #t) to (cond .. else); either is legal >Scheme, >> but chicken Scheme emits warnings on the former. > >(cond ... else) doesn't work in Guile 1.6 (it's why I coded them as >(cond .. #t) in the first place). > >> * Add the following as delimiters: #\' and #\` and #\. >> These are not required to be delimiters in Scheme, but >> they can be, and doing so means that we can detect syntax >errors >> of very dodgy constructs. This means that x'y will be >> considered an error, not a 3-char symbol. We can already >express >> that as |x'y|, and (x 'y) or x('y) work for making a list. >> * Optimize read-digits. >> * Improve Scheme error reporting when giving "Unexpected text >> after n-expression" by reporting the next (peeked) >character. >> * Add #!keyword-prefix and #!keyword-suffix support so can >handle >> syntax like STUFF: and :STUFF. >> * Modify Scheme sweet-run so that it returns the program exit >code. >> * Add type annotations in chicken format, and ensure it does >not >> interfere with other Schemes like guile. >> >> >> >------------------------------------------------------------------------------ >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk >Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> _______________________________________________ >> Readable-discuss mailing list >> Rea...@li... >> https://lists.sourceforge.net/lists/listinfo/readable-discuss --- David A.Wheeler |