delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:3950 |
From: | dmason AT scs DOT ryerson DOT ca (Dave Mason) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Unused functions & slow linking? |
Date: | 16 May 1996 22:58:05 GMT |
Organization: | Ryerson Polytechnic University |
Lines: | 19 |
Message-ID: | <DMASON.96May16185805@jupiter.scs.ryerson.ca> |
References: | <199605160312 DOT XAA07094 AT delorie DOT com> |
NNTP-Posting-Host: | jupiter.scs.ryerson.ca |
In-reply-to: | dj@delorie.com's message of Thu, 16 May 1996 03:12:42 GMT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
In article <199605160312 DOT XAA07094 AT delorie DOT com> dj AT delorie DOT com (DJ Delorie) writes: > > Would it be a good idea to support function level linking ? > > Not for V2's libc, since we already manually split up the source files > to nearly eliminate unused functions from being linked in in the first > place. It's easier to write the code that way than to teach the > linker to fix it for you. Most code falls into one of two categories: > > 1. Part of a library. Manually split the code into many sources once, > and every user benefits. > > 2. Part of an application. Hey, you're going to use them all anyway > or you wouldn't have written them, right? I presume this factorization into functions is the reason that the linker is so slow. It seems a *lot* slower than with V1.(13?). .../Dave
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |