[previous] [up] [next]     [index]
Next: is-busy? Up: Miscellaneous Previous: get-window-text-extent

graphical-read-eval-print-loop

Similar to MzScheme's read-eval-print-loop, except that none of read-eval-print-loop's configuration parameters are used (such as current-read) and the interaction occurs in a GUI window instead of using the current input and output ports.

Expressions entered into the graphical read-eval-print loop can be evaluated in an eventspace (and thread) that is distinct from the one implementing the graphical-read-eval-print-loop window (i.e., the current eventspace when graphical-read-eval-print-loop is called).

If no eventspace is provided, or if #f is provided, an evaluation eventspace is created using (make-eventspace) with a new custodian; the eventspace and its threads are be shut down when the user closes the graphical-read-eval-print-loop window. The following parameters are initialized in the created eventspace's handler thread:

See (see parameters) for more information about these parameters.

If an evalaution eventspace is provided to graphical-read-eval-print-loop, the parameters are not set (but evaluation output still goes to the new frame).

The keymap for the read-eval-print loop's editor is initialized by calling the current keymap initializer procedure, which is determined by the current-text-keymap-initializer parameter.



PLT