Re: Where to put dynamic-link etc in docs?

[Neil Jerram]

>>>>> "Marius" == Marius Vollmer <address@hidden> writes:

    Marius> Hi, what would be the best place in the manual to put the
    Marius> documentation about dynamic-link, dynamic-calll, etc?

    Marius> Currently, they are documented along with the module
    Marius> system, but that feels wrong, since dynamic linking is
    Marius> independent from the module system.

    Marius> It would fit into a `operating system access' section, or
    Marius> something.

Here's two possibilities:

(i) Generalize the existing "Read/Load/Eval" chapter so that it covers
the "loading" of non-Scheme code as well, and put the dynamic linking
doc as a section into that chapter.

(ii) Add the dynamic linking doc as a new chapter just after
"Read/Load/Eval".

I don't think that an `operating system access' section would work so
well, because there are already bits of operating system access
scattered elsewhere, e.g. open-*-file in the I/O chapter and threads
in the Scheduling chapter.

What do you think?

        Neil