Changeset 34354 in project


Ignore:
Timestamp:
08/25/17 17:58:47 (4 weeks ago)
Author:
kon
Message:

rel 2.2.2 / 2.2.1

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/eggref/4/mailbox

    r34299 r34354  
    218218
    219219* A "deadlock" situation is possible when using {{mailbox-wait!}},
    220 {{mailbox-recieve!}}, or {{mailbox-cursor-next}} should there be no other
     220{{mailbox-receive!}}, or {{mailbox-cursor-next}} should there be no other
    221221threads "runnable." The problem is when the mailbox is empty the current-thread
    222222is suspended (indefinite block). When the scheduler looks for the next ready
     
    224224allow the calling thread to unblock eventually.
    225225
     226* Cannot wait with timeout on the primordial thread. So {{mailbox-wait!}},
     227{{mailbox-receive!}}, and {{mailbox-cursor-next}} must not be used when the
     228{{(current-thread)}} is the {{##sys#primordial-thread}}.
     229
    226230* A mailbox-cursor must live in an environment where mailbox entries are
    227231added and removed asynchronously. The cursor does '''not''' see a
     
    243247== Version history
    244248
     249; 2.2.2 : Wait with timeout on the primordial thread is an error.
     250; 2.2.1 :
    245251; 2.2.0 : Included ''inline-type-checks.scm'' so all includes are egg-local.
    246252; 2.1.3 : Fix for resuming a thread when mailbox empty; reported by Jeronimo Pellegrini. Added {{mailbox-cursor-unwound?}}. The {{mailbox-name}} can be an arbitrary Scheme object.
Note: See TracChangeset for help on using the changeset viewer.