| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DSO Terms Galore |
| Date: | 2024-07-19 19:46:28 |
| Message-ID: | ZprClMExXZGxsAKb@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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? Or perhaps, what *should* it
> be? "Module"? "Library"? "Object"? "Shared ____"? "Dynamic ____"?
>
> Would it be useful to decide on one term (perhaps with "file" appended
> where it refers to a file that contains one of these things) and
> standardize the docs?
The lack of consistent terminology seems at least potentially confusing for
readers. My first reaction is that "shared library" is probably fine.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-07-19 19:48:10 | Re: Report search_path value back to the client. |
| Previous Message | Jeff Davis | 2024-07-19 19:41:49 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |