cvs.gedasymbols.org/archives/browse.cgi | search |
From: | "Morpheus" <hall AT silo DOT csci DOT unt DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | difference between libraries and headers |
Date: | Wed, 17 Nov 1999 18:38:10 -0600 |
Organization: | University of North Texas |
Lines: | 16 |
Message-ID: | <80vhq4$kvc@hermes.acs.unt.edu> |
NNTP-Posting-Host: | dfw-premium-13.dialup.unt.edu |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Newsreader: | Microsoft Outlook Express 5.00.2314.1300 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.2314.1300 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I know the difference between a library file and a header file, but can someone tell me the particulars involved -- the differences between compiling your program with included headers and including a library on the prompt? I know the header files on the include path don't contain a full implementation of their functions/classes, so where is this implementation? If it's in the library files, how does the compiler know which library to get without specifying it at the prompt? If compiling with libraries and headers are independent things, then what is the advantage of compiling with library files? Thanks. Morpheus hall AT cs DOT unt DOT edu http://people.unt.edu/~dahall
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |