Xref: utzoo comp.os.msdos.programmer:3826 comp.lang.fortran:4940 comp.lang.pascal:5667 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!mahendo!jato!vsnyder From: vsnyder@jato.jpl.nasa.gov (Van Snyder) Newsgroups: comp.os.msdos.programmer,comp.lang.fortran,comp.lang.pascal Subject: Re: Wanted: Replacement linker for msdos. Message-ID: <1991Mar9.010104.16188@jato.jpl.nasa.gov> Date: 9 Mar 91 01:01:04 GMT References: <2635@bnlux0.bnl.gov> Reply-To: vsnyder@jato.Jpl.Nasa.Gov (Van Snyder) Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 32 In article <2635@bnlux0.bnl.gov> kushmer@bnlux0.bnl.gov (christopher kushmerick) writes: > >Are there any good public domain, shareware or commercial replacement linkers? > Try the OptLink linker from SLR Systems. It's 5-10 times faster than the DOS linker. > >I am using Ryan McFarland fortran, together with a callms (call micro soft) >kludge, to call some routines in an ms comaptible library. I use the linker >PLINK86plus, the P standing for Pro, I think (as in profort). > I don't know exactly where to get the SLR linker. I got it with my Lahey compiler. I HAD an RM compiler at one time. It pooped out one of those messages that says: "A compiler error has occurred. This shouldn't happen. Please contact RM immediately." So I did. 18 months later, I got a polite form letter inviting me to BUY their next upgrade. By then, I'd been using Lahey's compiler for 15 months. Lahey's compiler is about 4 times faster than RM's. Lahey's debugger isn't code-view, but it's very useful nonetheless. I once had a bug in complex arithmetic, and called Lahey about it. In ONE HOUR they called back, and said "type this ... into your .FIX" file. I said "my WHAT file?" Turns out there's an ascii file the compiler reads and patches itself before it runs. How's that for service? I've only worked with two folks that have that quality service: Lahey and WordPerfect. End of commercial. Regards. -- vsnyder@jato.Jpl.Nasa.Gov ames!elroy!jato!vsnyder vsnyder@jato.uucp