| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | andrew(dot)dunstan(at)2ndquadrant(dot)com |
| Cc: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: late binding of shared libs for C functions |
| Date: | 2018-06-12 14:35:59 |
| Message-ID: | CAEzk6ffvUREfF4aZbMnrd=rtjOgk1RYdkUAyV5xZPB5XEDjnNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 12 Jun 2018 at 13:41, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> On 06/12/2018 06:48 AM, Geoff Winkless wrote:
> > + | AS 'obj_file', 'link_symbol' [UNBOUNDED]
> > (I know UNBOUNDED isn't quite the word - BINDLATE would be better -
> > but I figured I should try to use an existing reserved keyword...)
>
> UNBOUNDED would be terrible. It does not mean the same thing as UNBOUND.
Indeed. I agree.
> Perhaps something like NO CHECK would meet the case, i.e. we're not
> checking the link at function creation time.
I did wonder about "NO CHECK" but wasn't sure if having two words
would make the parser change more complex.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2018-06-12 14:40:33 | Re: pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development |
| Previous Message | Jonathan S. Katz | 2018-06-12 14:21:29 | Re: pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development |