From owner-freebsd-hackers  Sun Oct  5 16:34:15 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA16375
          for hackers-outgoing; Sun, 5 Oct 1997 16:34:15 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16316;
          Sun, 5 Oct 1997 16:32:54 -0700 (PDT)
          (envelope-from tlambert@usr05.primenet.com)
Received: (from tlambert@localhost)
	by usr05.primenet.com (8.8.5/8.8.5) id QAA23789;
	Sun, 5 Oct 1997 16:32:50 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199710052332.QAA23789@usr05.primenet.com>
Subject: Re: link tables and scope
To: cmott@srv.net (Charles Mott)
Date: Sun, 5 Oct 1997 23:32:50 +0000 (GMT)
Cc: freebsd-hackers@FreeBSD.ORG, ari@suutari.iki.fi, brian@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.96.971004113214.23797B-100000@darkstar.home> from "Charles Mott" at Oct 4, 97 11:41:26 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> What I observe is that the link symbol table (I don't
> know a better word for it), contains function names
> both in alias.h and alias_local.h.  Is there any way
> to somehow restrict the scope of some globals in a
> library so that they cannot be linked by modules outside
> the library.
> 
> The only way I know to do this is put the entire library
> in a single file and make as much as possible static.

man ld
/-r 
   ^
   |
   space before hitting return.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.