-(define-module (loopy agenda)
+(define-module (eightsync agenda)
#:use-module (srfi srfi-1)
#:use-module (srfi srfi-9)
#:use-module (srfi srfi-9 gnu)
schedule-segments-split schedule-extract-until!
add-segments-contents-to-queue!
+ %sync 8sync %sync-at 8sync-at %sync-delay 8sync-delay
+
<run-request>
make-run-request run-request?
run-request-proc run-request-when
- run-it wrap run run-at delay
+ run-it wrap run run-at run-delay
%current-agenda
start-agenda agenda-run-once))
(time agenda-time))
(define (make-async-prompt-tag)
+ "Make an async prompt tag for an agenda.
+
+Generally done automatically for the user through (make-agenda)."
(make-prompt-tag "prompt"))
(define* (make-agenda #:key
read-port-map write-port-map except-port-map
schedule time))
+(define (current-agenda-prompt)
+ "Get the prompt for the current agenda; signal an error if there isn't one."
+ (let ((current-agenda (%current-agenda)))
+ (if (not current-agenda)
+ (throw
+ 'no-current-agenda
+ "Can't get current agenda prompt if there's no current agenda!")
+ (agenda-prompt-tag current-agenda))))
+
\f
;;; Schedule
(lambda ()
body ...))
+;; @@: Do we really want `body ...' here?
+;; what about just `body'?
(define-syntax-rule (run body ...)
"Run everything in BODY but wrap in a convenient procedure"
(make-run-request (wrap body ...) #f))
"Run BODY at WHEN"
(make-run-request (wrap body ...) when))
+;; @@: Is it okay to overload the term "delay" like this?
+;; Would `run-in' be better?
(define-syntax-rule (run-delay body ... delay-time)
"Run BODY at DELAY-TIME time from now"
(make-run-request (wrap body ...) (tdelta delay-time)))
-(define (delay run-request delay-time)
- "Delay a RUN-REQUEST by DELAY-TIME"
- (set-field run-request
- (run-request-when)
- (tdelta delay-time)))
+
+\f
+;;; Asynchronous escape to run things
+;;; =================================
+
+;; The future's in futures
+
+(define (make-future call-first on-success on-fail on-error)
+ ;; TODO: add error stuff here
+ (lambda ()
+ (let ((call-result (call-first)))
+ ;; queue up calling the
+ (run (on-success call-result)))))
+
+(define (agenda-on-error agenda)
+ (const #f))
+
+(define (agenda-on-fail agenda)
+ (const #f))
+
+(define* (request-future call-first on-success
+ #:key
+ (agenda (%current-agenda))
+ (on-fail (agenda-on-fail agenda))
+ (on-error (agenda-on-error agenda))
+ (when #f))
+ ;; TODO: error handling
+ ;; do we need some distinction between expected, catchable errors,
+ ;; and unexpected, uncatchable ones? Probably...?
+ (make-run-request
+ (make-future call-first on-success on-fail on-error)
+ when))
+
+(define-syntax-rule (%sync body args ...)
+ "Run BODY asynchronously at a prompt, passing args to make-future.
+
+Pronounced `async' despite the spelling.
+
+%sync was chosen because (async) was already taken and could lead to
+errors, and this version of asynchronous code uses a prompt, so the `a'
+character becomes a `%' prompt! :)
+
+The % and 8 characters kind of look similar... hence this library's
+name! (There are 8sync aliases if you prefer that name.)"
+ (abort-to-prompt (current-agenda-prompt)
+ (wrap body)
+ args ...))
+
+(define-syntax-rule (%sync-at body when args ...)
+ (abort-to-prompt (current-agenda-prompt)
+ (wrap body)
+ #:when when
+ args ...))
+
+(define-syntax-rule (%sync-delay body delay-time args ...)
+ (abort-to-prompt (current-agenda-prompt)
+ (wrap body)
+ #:when (tdelta delay-time)
+ args ...))
+
+(define-syntax-rule (8sync args ...)
+ "Alias for %sync"
+ (%sync args ...))
+
+(define-syntax-rule (8sync-at args ...)
+ "Alias for %sync-at"
+ (%sync-at args ...))
+
+(define-syntax-rule (8sync-delay args ...)
+ "Alias for %sync-delay"
+ (8sync-delay args ...))
+
\f
;;; Execution of agenda, and current agenda
(agenda-prompt-tag agenda)
(lambda ()
(proc))
- ;; TODO
- (lambda (k) k)))
+ (lambda* (resume-with please-run-this . args)
+ (apply request-future please-run-this resume-with
+ args))))
(let ((queue (agenda-queue agenda))
(next-queue (make-q)))