X-Git-Url: https://jxself.org/git/?a=blobdiff_plain;f=loopy.scm;h=2f733c01d4fe32afa21641bc456c37efc4f0f171;hb=35a90099f27585e853a8b8aee498c5228d8f9697;hp=6f1516fdb51449be60c4c952b2d024b97369e968;hpb=79592dc135a74a704398a7a045dad5d633d42966;p=8sync.git diff --git a/loopy.scm b/loopy.scm index 6f1516f..2f733c0 100644 --- a/loopy.scm +++ b/loopy.scm @@ -15,7 +15,11 @@ make-time-segment time-segment? time-segment-time time-segment-queue - time-< time-= time-<= + time-< time-= time-<= time-+ + + + make-time-delta time-delta? + time-delta-sec time-delta-usec make-schedule schedule? @@ -86,7 +90,7 @@ ;;; This is where we handle timed events for the future -;; This section totally borrows from SICP +;; This section totally borrows from the ideas in SICP ;; <3 <3 <3 ;; NOTE: time is a cons of (seconds . microseconds) @@ -127,6 +131,21 @@ (or (time-< time1 time2) (time-= time1 time2))) + +(define-record-type + (make-time-delta-intern sec usec) + time-delta? + (sec time-delta-sec) + (usec time-delta-usec)) + +(define* (make-time-delta sec #:optional usec) + (make-time-delta-intern sec (or usec 0))) + +(define (time-+ time time-delta) + (cons (+ (car time) (time-delta-sec time-delta)) + (+ (cdr time) (time-delta-usec time-delta)))) + + (define-record-type (make-schedule-intern segments) schedule? @@ -139,7 +158,7 @@ ;; mutates AND is worst case of O(n) in both space and time :( ;; but at least it'll be reasonably easy to refactor to ;; a more functional setup? -(define (schedule-add! time proc schedule) +(define (schedule-add! schedule time proc) (let ((time (time-segment-right-format time))) (define (new-time-segment) (let ((new-segment @@ -292,11 +311,12 @@ (agenda-run-once agenda)))) (if (and stop-condition (stop-condition agenda)) 'done - (loop - ;; Adjust the agenda's time just in time - ;; We do this here rather than in agenda-run-once to make - ;; agenda-run-once's behavior fairly predictable - (set-field new-agenda (agenda-time) (gettimeofday))))))) + (let ((updated-agenda + ;; Adjust the agenda's time just in time + ;; We do this here rather than in agenda-run-once to make + ;; agenda-run-once's behavior fairly predictable + (set-field new-agenda (agenda-time) (gettimeofday)))) + (loop updated-agenda)))))) (define (agenda-run-once agenda) "Run once through the agenda, and produce a new agenda @@ -316,11 +336,21 @@ based on the results" (proc-result (call-proc proc)) (enqueue (lambda (run-request) - (cond - ((run-request-when run-request) - (error "TODO")) - (else - (enq! next-queue (run-request-proc run-request))))))) + (define (schedule-at! time proc) + (schedule-add! (agenda-schedule agenda) time proc)) + (let ((request-time (run-request-when run-request))) + (match request-time + ((? time-delta? time-delta) + (let ((time (time-+ (agenda-time agenda) + time-delta))) + (schedule-at! time (run-request-proc proc)))) + ((? integer? sec) + (let ((time (cons sec 0))) + (schedule-at! time (run-request-proc proc)))) + (((? integer? sec) . (? integer? usec)) + (schedule-at! request-time (run-request-proc proc))) + (#f + (enq! next-queue (run-request-proc run-request)))))))) ;; @@: We might support delay-wrapped procedures here (match proc-result ;; TODO: replace procedure with something that indicates @@ -334,6 +364,7 @@ based on the results" new-procs)) ;; do nothing (_ #f)))) - ;; TODO: Selecting on ports would happen here? + ;; TODO: Alternately, we could return the next-queue + ;; along with changes to be added to the schedule here? ;; Return new agenda, with next queue set (set-field agenda (agenda-queue) next-queue)))