Some notes on vars
This commit is contained in:
parent
679d2552a9
commit
87f243b16a
1 changed files with 15 additions and 0 deletions
15
tryme.scm
15
tryme.scm
|
@ -5,6 +5,21 @@
|
||||||
(ordo task)
|
(ordo task)
|
||||||
(ordo handler))
|
(ordo handler))
|
||||||
|
|
||||||
|
;; TODO: Consider how vars might be used in task args Currently a task argument
|
||||||
|
;; can be a context refrence, for example we could write:
|
||||||
|
;;
|
||||||
|
;; (install-directory (context-ref 'base-dir))
|
||||||
|
;;
|
||||||
|
;; but there's no way to nest these, so we this will not work:
|
||||||
|
;;
|
||||||
|
;; (install-file (file-name-join (context-ref 'base-dir) "foo"))
|
||||||
|
;;
|
||||||
|
;; Maybe we could implement something like:
|
||||||
|
;;
|
||||||
|
;; (install-file (context-fn (file-name-join (context-ref 'base-dir) "foo")))
|
||||||
|
;;
|
||||||
|
;; where context-fn is some syntax that returns (lambda (ctx) ...)
|
||||||
|
|
||||||
(define test-play
|
(define test-play
|
||||||
(play "Test play"
|
(play "Test play"
|
||||||
#:connection (local-connection)
|
#:connection (local-connection)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue