Re: Help- selective symbol exposure after link

rfg@monkeys.com (Ronald F. Guilmette)
27 Feb 1997 00:34:03 -0500

          From comp.compilers
Related articles
[12 earlier articles]
Re: Help- selective symbol exposure after link Dave@occl-cam.demon.co.uk (Dave Lloyd) (1997-02-07)
Re: Help- selective symbol exposure after link fjh@murlibobo.cs.mu.OZ.AU (1997-02-08)
Re: Help- selective symbol exposure after link ok@cs.rmit.edu.au (1997-02-11)
Re: Help- selective symbol exposure after link pfox@lehman.com (Paul David Fox) (1997-02-11)
Re: Help- selective symbol exposure after link jan@fsnif.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) (1997-02-16)
Re: Help- selective symbol exposure after link Dave@occl-cam.demon.co.uk (Dave Lloyd) (1997-02-20)
Re: Help- selective symbol exposure after link rfg@monkeys.com (1997-02-27)
| List of all articles for this month |
From: rfg@monkeys.com (Ronald F. Guilmette)
Newsgroups: comp.compilers
Date: 27 Feb 1997 00:34:03 -0500
Organization: Infinite Monkeys & Co.
References: 97-01-183 97-01-212 97-02-047 97-02-073
Keywords: linker, design

Dave Lloyd <Dave@occl-cam.demon.co.uk> writes:
>>Name mangling in C++ is another
>>example of the limitations in most linkers (what is wanted is a
>>strong-typed linker).


Richard A. O'Keefe <ok@cs.rmit.edu.au> wrote:
>Oh, like the one the B6700 had about 30 years ago?
>(Type-safe linkage between Algol, Fortran, COBOL, &c.)
>Dear old BINDER, how I miss it.
>
>Is there any reason why an ELF/DWARF linker couldn't enforce type safety?


None whatsoever. In fact, DWARF contains all of the information you
would need to do this.
--


-- Ron Guilmette, Roseville, CA -------- Infinite Monkeys & Co. ------------
---- E-mail: rfg@monkeys.com -----------------------------------------------
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.