Partial application in C

[Steven Ryan]

Chant for the day: `Let's hear it for our guru!' `Gee! You are you!'

>Partial application is not poor programming practice.  Again, what I
>(still) wish to know is what machines/operating systems allow me to
>use this technique for implementing partial application, and which
>ones require one of the magic handshakes (a,b,c,d) listed above, and
>which machines make it totally impossible.

>From personal experience, CDC 170s use a single address space for code
and data. Any data can be executed and any code can be read/written. In fact,
the IO library does this extensively to load and unload subroutines during
execution. All 6x00s, 7600, 7x, and 17x cpus guarentee the instruction stack
(cache) is flushed by an RJ (return jump--call a subroutine) instruction.

200s use a single address space and permit individual pages to be locked,
but nobody bothers. The 205 cpu has a VSB (void stack and branch) instruction
to flush the instruction stack (cache).

180s do use locked pages in a segmented address space. I don't recall seeing
any operating system calls to change the page keys.