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

[Mark H Johnson <Mark_H_Johnson@raytheon.com>]

Robert I. Eachus wrote:

> Mark H Johnson wrote:
> 
>> No, they were actually subroutine calls. The compiler generated 
>> slightly different code for an "in segment" call and a "cross segment" 
>> call due to the indirection. The glue code (to do the lookup) was 
>> basically a system service done by the OS to facilitate activation of 
>> new segments.
> 
> 
> Technically not correct.  The compiler could "in line" some local calls, 
> but the binder couldn't. 
I did not mention the binder (which in many ways I equate to having a 
linker on Unix), just the compiler.

> What happened was that when a segment called 
> an entry point for which the local link was null, it trapped.  The trap 
> routine tried to snap the link using the current environment, and if it 
> failed, bounced out to the user.  You literally could, when an error of 
> this type occurred, change the search paths, or write the missing 
> routine, compile it, then continue from the condition.  Done it myself....
> 
Me to. That is why I described that mechanism in terms the OP would 
likely understand in a previous message.

   --Mark