Re: Use of GPL'd code with proprietary programs

[Lee Hollaar]

In article <x58ydqaift.fsf@lola.goethe.zz> David Kastrup <dak@gnu.org> writes:
>hollaar@faith.cs.utah.edu (Lee Hollaar) writes:
>
>> In article <x5vfguan46.fsf@lola.goethe.zz> David Kastrup <dak@gnu.org> 
>> writes:
>> >cstacy@news.dtpq.com (Christopher C. Stacy) writes:
>> >> I think you may have misspoken in the above paragraph, because
>> >> "dlopen" _is_ dynamic linking.
>> >
>> >man dlopen.  No symbols are resolved by dlopen in the caller.
>> 
>> man dlopen.  From the header on every page, at least on my system:
>> "Dynamic Linking Library Functions                     dlopen(3DL)"
>
>That must be about the most relevant part of a manual page imaginable.

Perhaps it gives some idea about what the creators of dlopen(), dlsym(),
and dlclose() thought their purpose was.  Or maybe people guess that
from the "dl" at the start of each function name.  (Hint: it probably
doesn't stand for "dumb luck".)

Or maybe not everybody agrees with your particular definition of what
dynamic linking requires ...