Re: Read Macro Characters and Packages


Mikko Heikelä wrote:
On Sun, 4 Jun 2006, Pascal Costanza wrote:
Tel A. wrote:
What is the cannonical method of "exporting" read macro characters from
packages?

I don't have the impression that changing the read table occurs so often that
there is a "canonical" approach for this. My guess would be that exporting
the read macro function, or maybe a function that performs the modification
of the read table, is better because it avoids surprises.

The latter is at least what CLSQL does for its sql syntax. It exports
functions enable-sql-reader-syntax, disable-sql-reader-syntax, and a
couple of other related functions. See the documentation for more
information on these and their "local" counterparts.

-Mikko

That's what I was leaning towards as well. I would expect that users
would want to explicitly have control to modify the read table. I just
wondered if perhaps the import itself was considered explicit enough.

Thank you

.

Relevant Pages

  • Re: Read Macro Characters and Packages
    ... On Sun, 4 Jun 2006, Pascal Costanza wrote: ... I don't have the impression that changing the read table occurs so often that there is a "canonical" approach for this. ... My guess would be that exporting the read macro function, or maybe a function that performs the modification of the read table, is better because it avoids surprises. ...
    (comp.lang.lisp)
  • Re: Read Macro Characters and Packages
    ... My guess would be that exporting ... the read macro function, or maybe a function that performs the modification ... wondered if perhaps the import itself was considered explicit enough. ... There seems to be a small missunderstang here: CL packages are about ...
    (comp.lang.lisp)
  • More Multiple Classes per File (was Pretty Format...)
    ... Uri Guttman wrote: ... setups to exercise the limits of these paradigms. ... I think key to all of this is that packages that contain subs intended ... exporting no symbols with EXPORTER. ...
    (comp.lang.perl.misc)
  • Re: Understanding CLOS Encapsulation
    ... exporting a class name only exports the symbol. ... accessor functions. ... class may have slots from different packages. ... it is not clear which one you would want to simply refer to as SLOT-X ...
    (comp.lang.lisp)
  • Re: Image versus package savers?
    ... exporting then backing up your packages frequently, ... Things that I consider risky include: newly changed external interfacing; failure of an MVP triad to open correctly; note that you should never save an image if the dreaded prim g2 garbage collector walkback appears. ...
    (comp.lang.smalltalk.dolphin)