On Jul 23, 2024, at 07:26, Peter Eisentraut wrote:
> Things like "object" or "object file" or probably wrong-ish. I understand an
> object file to be a .o file, which you can't dlopen directly.
Agreed.
Another option, however, is “dynamically shared object” (DSO), which
corresponds to the us
On 19.07.24 21:27, David E. Wheeler wrote:
I’m trying to understand the standard terms for extension libraries. There seem
too a bewildering number of terms used to refer to a shared object library, for
example:
* LOAD[1]:
* “shared library”
* “shared library file”
* dynamic_library_path
On Jul 19, 2024, at 15:46, Nathan Bossart wrote:
> The lack of consistent terminology seems at least potentially confusing for
> readers. My first reaction is that "shared library" is probably fine.
That’s the direction I was leaning, as well, but I thought I heard somewhere
that the project u
On Fri, Jul 19, 2024 at 03:27:49PM -0400, David E. Wheeler wrote:
> I´m trying to understand the standard terms for extension libraries.
> There seem too a bewildering number of terms used to refer to a shared
> object library, for example:
>
> [...]
>
> What is the standard term for these things
Hackers,
I’m trying to understand the standard terms for extension libraries. There seem
too a bewildering number of terms used to refer to a shared object library, for
example:
* LOAD[1]:
* “shared library”
* “shared library file”
* dynamic_library_path[2]:
* “dynamically loadable module
