Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!crdgw1!montnaro
From: montnaro@sprite.crd.ge.com (Skip Montanaro)
Newsgroups: comp.sys.isis
Subject: Re: ISIS suggestions
Message-ID: 
Date: 3 Oct 89 16:58:16 GMT
References: 
	<32799@cornell.UUCP>
Sender: news@crdgw1.crd.ge.com
Reply-To:  (Skip Montanaro)
Organization: GE Corporate Research & Development, Schenectady, NY
Lines: 33
In-reply-to: ken@gvax.cs.cornell.edu's message of 3 Oct 89 16:10:01 GMT

In article <32799@cornell.UUCP> ken@gvax.cs.cornell.edu (Ken Birman) writes:

   >* lib[12].a and mlib.a are poor choices.  Makes them difficult to
   >  install in a global place like /usr/local/lib.

   Ah.  Now, this is a tricky one. 

   ... long answer deleted ... 

I interpreted the statement as meaning the file names themselves were
unsuitable for installation in a global directory. A quick ls of
/usr/lib/*.a on my Sun reveals two things

    1. All archive library names begin with "lib", so they can be used with
       the -l flag of cc, f77, ld, ...

    2. Most archive names suggest their use, e.g. libtermcap.a,
       libsunwindow.a, ... 

I see nothing particularly wrong with requiring multiple libraries at link
time. There is some precedent for it already, with X and SunView, at least.
How about some more standard names like

	libisis1.a

	libisis2.a

	libisisutil.a

(Or something. I don't yet use ISIS, so I don't know the functionality
present in the libraries.)
--
Skip Montanaro (montanaro@crdgw1.ge.com)