Is there some standard way to query what's in a readtable?
#<READTABLE {2803E135}>
is hardly terribly easy to interpret :-)
--
(reverse (concatenate 'string ········@" "enworbbc"))
http://vip.hyperusa.com/~cbbrowne/wp.html
Rules of the Evil Overlord #159. "If I burst into rebel headquarters
and find it deserted except for an odd, blinking device, I will not
walk up and investigate; I'll run like hell."
<http://www.eviloverlord.com/>
In article <·······················@news2.giganews.com>,
<········@hex.net> wrote:
>Is there some standard way to query what's in a readtable?
>
>#<READTABLE {2803E135}>
>is hardly terribly easy to interpret :-)
No, there isn't any standard way to query what's in a readable. The
standard doesn't specify what it is that a readable contains, merely the
abstract behavior of the predefined input characters. That's why there's
no GET-SYNTAX function, just SET-SYNTAX-FROM-CHAR -- you can't get an entry
as a first-class object, merely copy it to another character.
You could try using (describe *readtable*), but I doubt it will do anything
too useful.
--
Barry Margolin, ······@genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
········@hex.net writes:
> Is there some standard way to query what's in a readtable?
>
> #<READTABLE {2803E135}>
> is hardly terribly easy to interpret :-)
DESCRIBE and INSPECT if you're just curious.
GET-[DISPATCH-]MACRO-CHARACTER and READTABLE-CASE for programming, but
there's no standard way to query the character syntax types (short of
writing clever code that does READ-FROM-STRING on test strings to
deduce the values).
--
Pekka P. Pirinen, Adaptive Memory Management Group, Harlequin Limited
Most people are about as happy as they make up their minds to be.