public vs. private

[Alan Coopersmith]

Daniel Stone wrote:
> The rationale is simple: if another library is using it, it is not
> private API, no matter how many underscores you put in front of the
> symbol, and no matter that you put a comment saying 'this is private
> API'.  It's simply not.

In a world where both libraries always come from the same source and
are always updated together, why not?   Of course, this is just one of
the many things the X source has always done that modularization will
break, but such is the madness we're heading towards.

-- 
	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering