🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.c
Article #3288

Re: Libraries specified in source?

#3288
From: D'Arcy J.M. Cain
Date: Sat, 23 Jan 1993 19:42
25 lines
1407 bytes
ray@astro.ocis.temple.edu (Ray Lauff) writes:
>line of the compiler call.  Of course, using make files can
>simplify the process, but why not just have a line in the 
>main program such as
>
>#library "/lib/libc.a"

Two problems I can think of right off.  How do you know that the
function you want is in that library on every system and how do
you know that the libraries reside in that directory?

>which would then alert the linker that that library will be 
>required.  DIGITAL supplies macro assembly programmers with
>this capibility (.library directive), but they recommend
>against using it since it makes moving library files a problem
>since all the source code would need to be updated.  Perhaps
>C could avoid this problem by putting them in an include file.

How is this easier than using the Make file?

-- 
D'Arcy J.M. Cain (darcy@druid.com)  |
D'Arcy Cain Consulting              |   There's no government
Toronto, Ontario, Canada            |   like no government!
+1 416 424 2871          DoD#0082   |
Technical Details
Message-ID: <1993Jan23.194202.20332@druid.uucp>
Path: arc1-ca.pugleaf.net!sparky!uunet!utcsri!geac!lethe!druid!darcy
References: <1993Jan21.182949.29796@cronkite.ocis.temple.edu>

Show Full Headers
Complete Article Headers
Newsgroups: comp.std.c
Path: arc1-ca.pugleaf.net!sparky!uunet!utcsri!geac!lethe!druid!darcy
From: darcy@druid.uucp (D'Arcy J.M. Cain)
Subject: Re: Libraries specified in source?
Message-ID: <1993Jan23.194202.20332@druid.uucp>
Date: Sat, 23 Jan 1993 19:42:02 GMT
References: <1993Jan21.182949.29796@cronkite.ocis.temple.edu>
Organization: D'Arcy Cain Consulting
Lines: 25