Re: Alternate file types for RUN ?

JF Mezei wrote:
Arne Vajhøj wrote:
When did you last see a static linked image on VMS ?

Run time libraries such as the C RTL are associated with the image at
link time. While you may be able to do tricks with logicals to use a
different file, the association is still static since symbols are
resolved at link time and the image will just branch to specific
addresses where the routine is expected to reside within the shareable
image.

This is qwuite diffferent from lib$find_image_symbol where nothing
happens at link time and the finding and resolving of symbols within
some image file is done truly at run time.

No and no.

Static linking means that the code of the library is in the
executable EXE.

Dynamic linking means that the code of the library is in a
shareable EXE.

Static linking is a concept practically unknown on VMS.

And there are not that big a difference between
the shareable images being referred to in the
executable image and using LIB$FIND_IMAGE_SYMBOL.
I assume that they both use the undocumented
SYS$IMGACT and SYS$IMGFIX. Your code are significant
different, but the mechanism to determine
what to load should be the same.

Arne
.

Relevant Pages

  • Re: Alternate file types for RUN ?
    ... resolved at link time and the image will just branch to specific ... executable EXE. ... Static linking is a concept practically unknown on VMS. ... I have many applications that link against OLB libraries. ...
    (comp.os.vms)
  • Re: Alternate file types for RUN ?
    ... Run time libraries such as the C RTL are associated with the image at ... resolved at link time and the image will just branch to specific ... happens at link time and the finding and resolving of symbols within ... some image file is done truly at run time. ...
    (comp.os.vms)