[Openmcl-devel] ccl 1.11.5 release
ron at flownet.com
Sat Dec 9 00:13:09 PST 2017
Why not just publish it on github? Why do you think you need to patch the CCL sources?
BTW, symbol reader macros are not that hard:
BTW2 CCL has a general “advice” mechanism that allows you to wrap a hook around any function. It’s not documented, but it’s not hard to reverse-engineer it. Just meta-point on ADVISE.
On Dec 9, 2017, at 12:07 AM, 73budden . <budden73 at gmail.com> wrote:
> Hi! I have a library of reader extensions I wrote several years ago.
> Its features are:
> - symbol readmacros. Many DSLs try to emply [ ] for their purposes and
> define #\[ as a macro-character. When one uses two such DSLs together,
> it is an issue. I disambiguate this by binding reader function to a
> symbol, not to a character, so I can use sql-dsl:[ sql query ] and
> json-dsl:[ json array ] in the same expression.
> - hook on interning a symbol. E.g. sometimes "trash" symbol occur when
> one tries to split a big package in two. It is convenient to hook on
> interning a symbol with specific name, and some CL implementations do
> not allow doing this by tracing "intern".
> - local package nicknames, like this:
> http://www.sbcl.org/manual/#Package_002dLocal-Nicknames (actually SBCL
> obtained them later than I published my lib).
> I made the lib portable initially, but noone expressed an interest, so
> now I only support it for SBCL. I would like to port it to be useful
> on CCL also. It is hard to implement portably (actualy it contains
> almost a full CL reader), but it is rather easy to patch an
> implementation to support those features.
> Is there a chance that such a patch for CCL would be accepted?
> 2017-11-30 2:07 GMT+03:00, R. Matthew Emerson <rme at acm.org>:
>> Hello everyone.
>> I'm pleased to announce that version 1.11.5 of Clozure Common Lisp is now
>> This release brings the 1.11 release up-to-date with current OS releases,
>> and contains numerous bug fixes.
>> The fasl file version has not changed, so there is no need to recompile all
>> your code.
>> With this release, CCL no longer relies on the old Subversion repository.
>> Although the old Subversion repository will remain online for the
>> foreseeable future, please be sure to look to GitHub for the most up-to-date
>> versions of CCL.
>> https://ccl.clozure.com/download.html contains the details of how to
>> download a copy. Alternatively, you may go straight to the GitHub release
>> page for 1.11.5 at https://github.com/Clozure/ccl/releases/tag/v1.11.5.
>> Development on Clozure CL has slowed greatly over the past couple of years,
>> but now is the time to revitalize it. This release is an initial step in
>> that direction.
>> Please use https://github.com/Clozure/ccl/issues to report bugs or
>> enhancement requests.
>> Clozure Associates has long supported the development of CCL. But CCL is
>> not now, nor has it ever been Clozure Associates' proprietary product. The
>> project welcomes and needs contributions from its users. Thus, if you'd be
>> interested in helping with CCL, by writing code, documentation, or by any
>> other means, please let me know how I can help you do that.
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel