[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: parser variables persist beyond { } scope
From: |
Neil Puttock |
Subject: |
Re: parser variables persist beyond { } scope |
Date: |
Fri, 31 Jul 2009 23:20:05 +0100 |
2009/7/31 Patrick McCarty <address@hidden>:
> I *think* that's true.
Hmm, what about primitive procedures? I wouldn't class these as
identifiers, but they'll also return #t:
#(display (defined? 'car))
=> #t
Since ly:parser-lookup returns EOL if it can't find the variable, the
following is probably a safer bet:
(define (parser-defined? x)
(not (null? (ly:parser-lookup parser x))))
Regards,
Neil
- Re: parser variables persist beyond { } scope, (continued)
- Re: parser variables persist beyond { } scope, Han-Wen Nienhuys, 2009/07/31
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/07/31
- Re: parser variables persist beyond { } scope, Han-Wen Nienhuys, 2009/07/31
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/07/31
- Re: parser variables persist beyond { } scope, Trevor Daniels, 2009/07/31
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/07/31
- Re: parser variables persist beyond { } scope, Trevor Daniels, 2009/07/31
- Re: parser variables persist beyond { } scope, Patrick McCarty, 2009/07/31
- Re: parser variables persist beyond { } scope,
Neil Puttock <=