gmane.lisp.editors.hints.devel

Re: Patch to support cmucl/unicode

Raymond Toy — 2011-01-28T06:30:17

Oh, for cmucl non-unicode, a simple change to the default
%make-readtable-iterator makes it work.  Just change get-macro-character
and get-dispatch-macro-character to %get-macro-character and
%get-dispatch-macro-character.  I'm not sure, but I think this is the
right solution for all lisps to make sure these functions return what
named-readtables wants.

Ray

Patch to support cmucl/unicode

Raymond Toy — 2011-01-28T06:07:15

The patch below adds support for cmucl/unicode.  This basically adds an
implementation of %make-readtable-iterator, updates %clear-readtable for
cmucl (like sbcl), a fix for %get-dispatch-macro-character, a fix for
%get-macro-character (like allegro).

With these changes (and a small change in named-readtables.lisp  that
has already been mentioned by Stas Boukarev last month. 

With these changes cmucl passes all 36 of the tests.

Oh, one thing.  I noticed that in %clear-readtable, the last sexp is
#+common-lisp.  CMUCL has the :common-lisp feature, so the table is set
twice.  Perhaps this is oversight and the reader conditional should be
#-(or allegro sbcl cmu)?

Ray

Change log:

 * Add implementation of %make-readtable-iterator for cmucl/unicode.
 * Implement %clear-readtable for cmucl.

 * Make %get-dispatch-macro-character return NIL where cmucl actually
   has #'lisp::dispatch-char-error.  It seems named-readtables wants
   this.
 * Update %get-macro-character for cmucl, which behaves like allegro
   h

named-readtables/SLIME interaction problem

Cyrus Harmon — 2011-01-27T21:41:30

I ran into a problem with SLIME where I was getting errors the second time I would compile a buffer with contents such as the following:


(cl:eval-when (:compile-toplevel :load-toplevel :execute)
 (ql:quickload 'named-readtables))

(defpackage #:reader-macro-test
  (:use #:cl))

(in-package #:reader-macro-test)

(eval-when (:compile-toplevel :load-toplevel :execute)
  (named-readtables:defreadtable readtable-test
    (:merge :standard)))

(named-readtables:in-readtable readtable-test)


It turns out that the problem has to do with the way SLIME deals with the style-warning that the defreadtable gives about overwriting the existing readtable. The defreadtable form clears out the bindings for the existing reader, then issues the warning. SLIME parses the buffer and picks up that we're in the #:reader-macro-test package and sets *readtable* to be the readtable that we've just clobbered and then in SLIMEs error/warning handling code it further frobs (a copy of) the (now empty-ish) readtable and then attempts t

[Patch]: CMUCL and Allegro 8.2 fixes

Stas Boukarev — 2010-12-09T10:09:43

The default value of error-p optional parameter for
excl:named-readtable was changed to T in Allegro 8.2, which causes
errors whenever find-readtable is called on non existent readtable.

CMUCL has an issue with ordering of loop initializations in the loop of
define-api macro. And the spec is quite confusing on how it really should behave.
The workaround is to use (progn x (loop ...)) instead of (loop initially x ...)

Regarding hyperdoc

Tobias C. Rittweiler — 2009-12-09T08:19:30

luis/lichtblau,

Wrt our discussion on yesterday's evening, I think that
REGISTER-DOCUMENTATION should probably become a macro which expands to
symbols in *PACKAGE* only -- in particular, it does not expand to
symbols from the HYPERDOC package so not to impose a runtime dependency.

Essentially that is to restore to the old ways of doing things --
although the API has changed somewhat.

I didn't (and still don't) like the set-some-magic-variables way as an
_interface_ which was the reason I came up with
REGISTER-DOCUMENTATION. It seems to be the right implementation choice,
though.

Are you d'accord?

  -T.

[ANN] Named Readtables 0.9

Tobias C. Rittweiler — 2009-10-10T10:29:52

The [editor-hints] project is pleased to announce _Named Readtables_.


What are Named Readtables?

  It's a library

       a) to help you to organize your readtable hacks, 
   
   and b) to help your development environment to deal with these hacks.

  For detailed information see [What are Named-Readtables?] in the
  documentation.


Foretaste

  DEFREADTABLE (analogously to DEFPACKAGE) can be used to specify the
  content of a readtable.

  IN-READTABLE (analogously to IN-PACKAGE) can be used to specify what
  readtable should be used while compiling a .lisp file.

  Named-Readtables has an API very much inspired by the existing API
  of packages. But see [Important API idiosyncrasies] in the
  documentation.


Documentation

  See [Named-Readtables Documentation].


Download

  darcs get http://common-lisp.net/project/editor-hints/darcs/named-readtables/


Release Notes

  The release was tagged as 0.9 even though it's actually pretty much a 1.0.

  Experience tells that no matter how much you try to p