Flow-control structures: Difference between revisions

=={{header|PicoLisp}}==

As this task asks for the documentation of common flow control structures, we

refer here to the online documentation for more complete descriptions and

examples.

Relevant functions are:

===fork===

[http://software-lab.de/doc/refF.html#fork fork] creates a child process

===task===

[http://software-lab.de/doc/refT.html#task task] installs a background task

consisting of an environment and a list of executable expressions

===alarm===

[http://software-lab.de/doc/refA.html#alarm alarm] schedules a timer, which

runs a given list of executable expressions when it expires

===abort===

[http://software-lab.de/doc/refA.html#abort abort] runs a given list of

executable expressions, and aborts processing it if it takes longer than

a given time

===quit===

[http://software-lab.de/doc/refQ.html#quit quit] immediately stops all

execution and returns to the top level read-eval-print loop, optionally

signaling an error

===protect===

[http://software-lab.de/doc/refP.html#protect protect] delays the processing

of signals while a given list of executable expressions is executed

===catch===

[http://software-lab.de/doc/refC.html#catch catch] prepares for receiving a

'throw' while running a given list of executable expressions

===throw===

[http://software-lab.de/doc/refT.html#throw throw] causes a non-local jump

to a specified 'catch' environment

===bye===

[http://software-lab.de/doc/refB.html#bye bye] exits the interpreter

===finally===

[http://software-lab.de/doc/refF.html#finally finally] specifies a list of

executable expressions, to be run when current processing is done, even if

a 'throw' or 'bye' was executed, or an error occurred.