doc corrections and clarifications

This commit is contained in:
Matthew Flatt 2010-06-29 09:25:10 -06:00
parent be38b69820
commit 7a7f545046
2 changed files with 15 additions and 4 deletions

View File

@ -338,9 +338,10 @@ following symbols:
@item{@indexed-scheme['handles-events] --- this snip can handle
keyboard and mouse events when it has the keyboard focus}
@item{@indexed-scheme['handles-all-mouse-events] --- this snip can handle
mouse events that touch the snip, even if the snip does not
have the keyboard focus}
@item{@indexed-scheme['handles-all-mouse-events] --- this snip can
handle mouse events that touch the snip or that immediately
follow an event that touches the snip, even if the snip does
not have the keyboard focus}
@item{@indexed-scheme['width-depends-on-x] --- this snip's display
width depends on the snip's x-@techlink{location} within the

View File

@ -103,5 +103,15 @@ Installs a function to be called on each custodian-registered item and
void *d);
}
where @var{d} is the second argument for @var{f}.}
where @var{d} is the second argument for @var{f}.
At-exit functions are run in reverse of the order that they are
added. An at-exit function is initially registered (and therefore runs
last) that flushes each file-stream output port.
An at-exit function should not necessarily apply the closer function
for every object that it is given. In particular, shutting down a
file-stream output port would disable the flushing action of the final
at-exit function. Typically, an at-exit function ignores most objects
while handling a specific type of object that requires a specific
clean-up action before the OS-level process terminates.}