Re: load and use a ".o" file?

[lifetime n00b <anonymous@yahoo.com>]

tmoran@acm.org wrote:
>   How about making the freshly generated "hithere" file a server program
> with remotely accessible procedures etc and use Annex E.

That would be horribly inefficient. Conceptually, the contents of these 
object files become part of the "main program" when they are loaded and 
share the same address space with the main program. For example, a call 
to a function normally involves putting the arguments on the stack, 
executing the function, and reading the return value from a register. In 
the distributed case, the partition containing the function must be 
located and placed on the stream, the arguments to the function are 
placed on the stream, the stream is sent to the receiving partition 
which executes the function locally, and the result of the function call 
is placed back on the stream which is then read as the return value.