| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] "Extension" versus "module" |
| Date: | 2011-02-15 04:02:40 |
| Message-ID: | DED8C233-CF02-41DE-AE3A-A967397AC487@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Feb 14, 2011, at 5:42 PM, Tom Lane wrote:
>> Remember also that not all modules out there on the net will have been
>> updated either, so we must be able to discuss "extension-izing a
>> module". (??)
>
> Right. So it seems like we ought to stick with more or less the
> existing terminology: those various components under contrib/ are
> modules. Some of them are also extensions, but not all.
The similarity of the meaning of the words "extension" and "module" is unfortunate, as it might be hard for one to remember which is which. But given the precedent of the word "module," I don't suppose there's much choice.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2011-02-17 20:28:37 | typo in ecpg.sgml |
| Previous Message | Tom Lane | 2011-02-15 01:42:40 | Re: [HACKERS] "Extension" versus "module" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2011-02-15 04:03:07 | Re: tsearch Parser Hacking |
| Previous Message | David E. Wheeler | 2011-02-15 04:00:24 | Re: why two dashes in extension load files |