From: David Kastrup <dak@gnu.org>
Date: Tue, 22 Nov 2011 13:20:14 +0000 (+0100)
Subject: Use *unspecified* and/or unspecified? instead of (begin)
X-Git-Tag: release/2.15.20-1~7
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=c4ce3c4d3a49983ba5bedf851b60ffc62a25891f;p=lilypond.git

Use *unspecified* and/or unspecified? instead of (begin)
---

diff --git a/scm/c++.scm b/scm/c++.scm
index 0ea05c944c..a8b0d00c7e 100644
--- a/scm/c++.scm
+++ b/scm/c++.scm
@@ -70,7 +70,7 @@
   (or (symbol? x) (boolean? x)))
 
 (define-public (void? x)
-  (eq? x (begin)))
+  (unspecified? x))
 
 ;; moved list to end of lily.scm: then all type-predicates are
 ;; defined.
diff --git a/scm/define-event-classes.scm b/scm/define-event-classes.scm
index ddf45a199a..65dbd38e4f 100644
--- a/scm/define-event-classes.scm
+++ b/scm/define-event-classes.scm
@@ -87,7 +87,7 @@
                            (hashq-ref ancestor-lookup
                                       (cadr heritage)
                                       '())))))
-  (begin))
+  *unspecified*)
 
 ;; TODO: Allow entering more complex classes, by taking unions.
 (define-public (ly:make-event-class leaf)
diff --git a/scm/music-functions.scm b/scm/music-functions.scm
index 69d3029de3..3ea1ba887d 100644
--- a/scm/music-functions.scm
+++ b/scm/music-functions.scm
@@ -841,7 +841,7 @@ void return value (i.e., what most Guile functions with `unspecified'
 value return).  Use this when defining functions for executing actions
 rather than returning values, to keep Lilypond from trying to interpret
 the return value."
-  `(define-syntax-function (void? (begin)) ,@rest #f (begin)))
+  `(define-syntax-function (void? *unspecified*) ,@rest *unspecified*))
 
 (defmacro-public define-event-function rest
   "Defining macro returning event functions.