Re: put slist in ltdl namespace

[Bob Friesenhahn]

On Sat, 18 Dec 2004, Ralf Wildenhues wrote:
> > Any non-public symbol from
> > libltdl should be lt__ scoped.  This should include any replacement
> > code for glibc functions.  Without the scoping, libltdl may conflict
> > with other libraries which also provide glibc replacement functions.
>
> I cannot see any code except for slist which has the problem.

The problem also exists for closedir, opendir, readdir, rewinddir, and 
seekdir.  These are not prefixed at all so that under MinGW they will 
interfere with the MSYS POSIX porting library (when it is used), or 
with other programs which include their own portability wrapper 
functions.

> Are you talking about "no prefix" vs. "prefix" or "lt_ prefix" vs. "lt__
> prefix"?
>
> My question was merely regarding the latter (and maybe the location of
> the replacement #defines).

It seems that "lt__" is the preferred prefix for private globals.  The 
replacement defines shouldn't appear in libltdl public headers since 
they may interfer with dependent applications.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen