Re: Making tab-complete.c easier to maintain

From: Greg Stark <stark(at)mit(dot)edu>
To: David Fetter <david(at)fetter(dot)org>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making tab-complete.c easier to maintain
Date: 2015-12-09 15:49:20
Message-ID: CAM-w4HO_1Qw-Ph8E75hp7A7mNyKnhnNMvmhK2Pv2SqJGoebNxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 9, 2015 at 2:27 PM, David Fetter <david(at)fetter(dot)org> wrote:
> Agreed that the "whole new language" aspect seems like way too big a
> hammer, given what it actually does.

Which would be easier to update when things change?
Which would be possible to automatically generate from gram.y?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-12-09 16:08:32 Re: Rework the way multixact truncations work
Previous Message Andres Freund 2015-12-09 15:41:52 Re: Rework the way multixact truncations work