delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/24/15:15:56

Xref: news2.mv.net comp.os.msdos.djgpp:6366
From: jching AT aloha DOT com (Jimen Ching)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How do I create my own libraries ?
Date: 24 Jul 1996 04:20:05 GMT
Organization: Coconut Wireless
Lines: 15
Message-ID: <4t489l$gjv@news.aloha.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960722074747 DOT 7625B-100000 AT is>
NNTP-Posting-Host: mango.aloha.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
>On Sun, 21 Jul 1996, Mike A. Harris wrote:
>> This posed an interesting learning experience.  So ever since then, when
>> coding libs, I've used one function per module.  This prevents unneeded
>> code from bloating executables.
>> Is this also true of DJGPP?  What about other compilers?  Should one always
>> code LIBs as one function per module source files?
>Yes, it's the same with DJGPP.  The DJGPP C library almost always puts 
>every function on its own source file for this reason.

Is this what the Standard C document suggests as an implementation?
Does the GCC distribution also have this problem?
--jc
--
Jimen Ching (WH6BRR)      jching AT aloha DOT com     wh6brr AT uhm DOT ampr DOT org

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019