home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.std.c
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!csn!news.den.mmc.com!traffic!kevin
- From: kevin@traffic.den.mmc.com (Kevin Rodgers)
- Subject: Re: Libraries specified in source?
- Message-ID: <1993Jan22.234158.22292@den.mmc.com>
- Sender: news@den.mmc.com (News)
- Nntp-Posting-Host: traffic.den.mmc.com
- Organization: Martin Marietta Western Internal Systems, Technical Operations
- References: <1993Jan21.182949.29796@cronkite.ocis.temple.edu> <1993Jan22.013725.5587@nntpd.lkg.dec.com>
- Date: Fri, 22 Jan 1993 23:41:58 GMT
- Lines: 16
-
- In article <1993Jan22.013725.5587@nntpd.lkg.dec.com> diamond@jit.dec.com (Norman Diamond) writes:
- >In article <1993Jan21.182949.29796@cronkite.ocis.temple.edu> ray@astro.ocis.temple.edu (Ray Lauff) writes:
- >>I often find myself wondering why standard C has no mechanisms for
- >>embedding the libraries required for loading into the code. Right
- >>now I have to specify them on the command line of the compiler call.
- ...
- >Surely the standard can't
- >specify how to use extensions.
-
- Surely the standard can evolve to include a few good ideas, like Ray's
- #library directive.
- --
- Kevin Rodgers kevin@traffic.den.mmc.com
- Martin Marietta MS A16401 (303) 790-3971
- 116 Inverness Dr. East
- Englewood CO 80112 USA GO BUFFS!
-