Re: [clisp-list] Implementation-dependent reader macros

[<pj...@in...>]

Didier Verna <di...@lr...> writes:

> Talking to myself:
>
> I wrote:
>
>> | #+ccl (#_this-should-not-bother-you-because-you-are-not-ccl 1)
>>
>> | *** - READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"test.lisp" @16>:
>> |       After #\# is #\_ an undefined dispatch macro character
>> | 
>> | zsh: exit 1     clisp test.lisp
>
>   After reading CLHS's entry for *read-suppress*, I'm afraid that clisp
> is right: "Dispatching macro characters continue to parse an infix
> numerical argument, and invoke the dispatch function.".
>
> So what would be your advice around this problem? I can for example
> conditionally add a file to my ASDF system, although this sounds a bit
> like using a bazooka to kill a mosquito...

I should add, the reason is that reader macro may read a unknown number
of forms following them.

Reading a  (#- #3_ a b c d e f g h)

there's no way to know what list will be read without a definition of
#_.

So the reader macro I advise to create should know its basic syntax,
ie. it should eat what it has to eat.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.