From: Christopher Allan Webber <cwebber@dustycloud.org>
Date: Wed, 18 Nov 2015 17:18:44 +0000 (-0600)
Subject: More comments and stub code
X-Git-Tag: v0.1.0~170
X-Git-Url: https://jxself.org/git/?a=commitdiff_plain;h=b64ff7b00037e87c5f30d89e502c02be0fc4dc20;p=8sync.git

More comments and stub code
---

diff --git a/loopy.scm b/loopy.scm
index 1b5e29d..9644699 100644
--- a/loopy.scm
+++ b/loopy.scm
@@ -6,12 +6,27 @@
 ;; @@: Using immutable agendas here, so wouldn't it make sense to
 ;;   replace this queue stuff with using pfds based immutable queues?
 
+;;; The agenda consists of:
+;;;  - a queue of immediate items to handle
+;;;  - sheduled future events to be added to a future queue
+;;;  - a tag by which running processes can escape for some asynchronous
+;;;    operation (from which they can be returned later)
+;;;  - a mapping of ports to various handler procedures
+;;;
+;;; The goal, eventually, is for this all to be immutable and functional.
+;;; However, we aren't there yet.  Some tricky things:
+;;;  - The schedule needs to be immutable, yet reasonably efficient.
+;;;  - Need to use immutable queues (ijp's pfds library?)
+;;;  - Modeling reading from ports as something repeatable,
+;;;    and with reasonable separation from functional components?
+
 (define-immutable-record-type <agenda>
-  (make-agenda-intern queue prompt-tag port-mapping)
+  (make-agenda-intern queue prompt-tag port-mapping schedule)
   agenda?
   (queue agenda-queue)
   (prompt-tag agenda-prompt-tag)
-  (port-mapping agenda-port-mapping))
+  (port-mapping agenda-port-mapping)
+  (schedule agenda-schedule))
 
 (define (make-async-prompt-tag)
   (make-prompt-tag "prompt"))
@@ -19,9 +34,51 @@
 (define* (make-agenda #:key
                       (queue (make-q))
                       (prompt (make-prompt-tag))
-                      (port-mapping (make-port-mapping)))
+                      (port-mapping (make-port-mapping))
+                      (schedule (make-schedule)))
   (make-agenda-intern queue prompt port-mapping))
 
+
+;;; Schedule
+;;;
+;;; This is where we handle timed events for the future
+
+;; This section totally borrows from SICP
+;; <3 <3 <3
+
+;; NOTE: time is a cons of (seconds . microseconds)
+
+(define-record-type <time-segment>
+  (make-time-segment-intern time queue)
+  time-segment?
+  (time time-segment-time)
+  (queue time-segment-queue time-segment-set-queue!))
+
+(define* (make-time-segment time #:optional (queue (make-q)))
+  (let ((time (match time
+                ;; time was just an integer (just the second)
+                ((? integer? _) (cons time 0))
+                ;; time is already a cons of second and microsecnd
+                (((? integer? s) (? integer? u)) time)
+                (_ (throw 'invalid-time "Invalid time" time)))))
+    (make-time-segment-intern time queue)))
+
+(define (make-schedule)
+  '())
+
+(define (schedule-add-new-segment! schedule time)
+  (error))
+
+(define (schedule-add! schedule time proc)
+  ;; Find and add a schedule segment
+  (error))
+
+(define (schedule-empty? schedule)
+  (eq? schedule '()))
+
+
+;;; Port handling
+
 (define (make-port-mapping)
   (make-hash-table))
 
@@ -47,6 +104,9 @@
   "Whether this port-mapping contains any elements"
   (not (port-mapping-empty? port-mapping)))
 
+
+;;; Execution of agenda, and current agenda
+
 (define %current-agenda (make-parameter #f))
 
 (define* (start-agenda agenda #:optional stop-condition)