Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!nike!ucbcad!ucbvax!RELAY.CS.NET!LLACROIX%carleton.edu From: LLACROIX%carleton.edu@RELAY.CS.NET (Les LaCroix) Newsgroups: mod.computers.vax Subject: Re: Re: Missing VMS 4.4 VAXCRT[lg].OLB files Message-ID: <8609201128.AA03986@ucbvax.Berkeley.EDU> Date: Fri, 19-Sep-86 00:48:00 EDT Article-I.D.: ucbvax.8609201128.AA03986 Posted: Fri Sep 19 00:48:00 1986 Date-Received: Sat, 20-Sep-86 20:41:38 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 47 Approved: info-vax@sri-kl.arpa In a recent note to jayb%zeus.tek.csnet@csnet-relay.csnet (cc to info-vax) regarding VAXCRTL object libraries vs the corresponding shraed images, you state: > There is NO advantage to using the object library, rather than the shareable > library, except in rather rare cases (linking an image that will work on older > versions of VMS, for example - and even then, just having the C library in > object form is often not enough. Better to ship object files of your code and > link on the target system if this is the problem.) Using the shareable images > has a number of advantages, including smaller images and the fact that images > pick up bug fixes to the support routines without re-linking. Two small objections here: 1) You get smaller images and RTL bug fixes, all w/o relinking. You also get an extra image to be activated every time you run your application. In most cases that's not worth worrying about. Then there are those rare times when it *does* matter. 2) In addition to the bug fixing that comes along with VMS updates, it's not unheard of to see new bugs introduced. Yes, even from DEC, and yes in the RTLs. A product of my employer's was hit with such a problem with VMS 4.4. Fortunately the problem was only annoying and had no consequential impact for our customers. Even more fortunate is the fact that these kinds of problems are very rare. Conclusion: know your options and the implications, then use the shared images unless you have a *really* good reason to do otherwise. > Further, Is there a command to given to create the .OLB from the .EXE > libraries. > No. .EXE libraries contain executable code; .OLB's, object code. You would > need an inverse to the linker. True, but sometimes you can fake it by creating a Shared Image Library which contains references to the shared images you want to link against. Your program still gets linked to the shared images, but you can usually avoid a Linker Options file. Unfortunately, there have been documented problems in the past with shared image libraries which refer to VAXCRTL.EXE. I don't know if the problems still exist in VMS 4.4. Les LaCroix | csnet: llacroix@carleton.edu SPSS, Inc. | uucp: ...{ihnp4,decvax}!stolaf!ccnfld!llacroix 402 Washington Street | ...ihnp4!gargoyle!spsspyr!lacroix Northfield, MN 55057-2027 | "A dog is a dog until he faces you. Then he is Mr. Dog." - haitian farmer