| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: YAML |
| Date: | 2009-12-08 14:17:59 |
| Message-ID: | 603c8f070912080617p145725c8n27ac53f5432ad4a1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 8, 2009 at 9:13 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Well, if we're going to commit this, as now appears likely, we should have
> some language lawyers go over our code for both YAML and JSON with a fine
> tooth comb to make sure what we are producing is strictly According To
> Hoyle.
+1. I'm a little concerned about the bit about the YAML specification
changing, too, but at least if we can ensure that we're compliant with
the spec that is current at the time the code goes in we have a leg to
stand on.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-12-08 14:23:16 | Streaming replication and non-blocking I/O |
| Previous Message | Andrew Dunstan | 2009-12-08 14:13:10 | Re: YAML |