[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly |
Date: |
Sun, 12 Jan 2014 20:27:18 +0000 |
Comment #1 on issue 3799 by address@hidden: Avoid macro at top-level in
ly/satb.ly
http://code.google.com/p/lilypond/issues/detail?id=3799
Checking definedness in a macro works fine in Guile 2; what doesn't work is
doing it at runtime, e.g. (if (defined? 'x) x #f), because Guile complains
about the undefined variable while compiling. But even that works in
(define x (if (defined? 'x) x y)), which if how Guile 2 implements
define-once.
...but define-once is clearer anyway. I'll make a patch.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/12
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly,
lilypond <=
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/13
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/13
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/13
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/13
- Re: [Lilypond-auto] Issue 3799 in lilypond: Avoid macro at top-level in ly/satb.ly, lilypond, 2014/01/15