home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!news.u.washington.edu!glia!hawkeye
- From: hawkeye@glia.biostr.washington.edu (Ken Keys - TF Dude)
- Newsgroups: comp.std.c
- Subject: Re: Libraries specified in source?
- Message-ID: <hawkeye.727994342@glia>
- Date: 25 Jan 93 20:39:02 GMT
- Article-I.D.: glia.hawkeye.727994342
- References: <1993Jan21.182949.29796@cronkite.ocis.temple.edu> <1993Jan23.194202.20332@druid.uucp> <1993Jan25.152432.7022@crd.ge.com>
- Organization: University of Washington
- Lines: 34
- NNTP-Posting-Host: glia.biostr.washington.edu
-
- In <1993Jan25.152432.7022@crd.ge.com> volpe@bart.NoSubdomain.NoDomain (Christopher R Volpe) writes:
-
- >|> ray@astro.ocis.temple.edu (Ray Lauff) writes:
- >|> >simplify the process, but why not just have a line in the
- >|> >main program such as
- >|> >
- >|> >#library "/lib/libc.a"
-
- >I like the idea, though I wouldn't include path names for standard stuff.
- >Rather, I would mimic the semantics for #include directives.
-
- >Similarly, I would prefer to see something like:
- > #include <libm.a>
-
- >to get the math library.
-
- Even better, math.h could contain the line
-
- #library <libm.a>
-
- That way, a program conforming to the current standard would work with
- this new compiler without modification. New programs wouldn't have to
- use the new #library directive, so they'll work just fine under current
- compilers (with the -l switch, of course).
-
- --
- Ken Keys, aka Hawkeye
- Master of the Fugue
- kkeys@ucsd.edu or hawkeye@ucsd.edu
- --
- --
- Ken Keys, aka Hawkeye
- Master of the Fugue
- kkeys@ucsd.edu or hawkeye@ucsd.edu
-