| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: leakproof |
| Date: | 2012-02-20 01:42:04 |
| Message-ID: | 15911.1329702124@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Feb 19, 2012 at 5:29 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> Can we come up with a more descriptive term?
> We bikeshed on that topic a while back and nobody suggested anything
> that got more than 1 or 2 votes. But I'm still happy to rename it if
> we can come up with something better, because I'm not in love with it
> either.
> Having now spent far too much time in bed with that patch, I'm feeling
> like the concept that we are really looking for there is what some
> languages call "pure" - that is, there must be no side effects,
> whether by throwing exceptions or otherwise.
Hmm, "pure" doesn't sound bad to me. Nice and short.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Billy Earney | 2012-02-20 02:13:14 | Re: Future of our regular expression code |
| Previous Message | Tom Lane | 2012-02-20 01:40:17 | Re: Future of our regular expression code |