Re: BUG #14167: ecpg parser cann't ignore code in #ifdef ?

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: 德哥 <digoal(at)126(dot)com>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14167: ecpg parser cann't ignore code in #ifdef ?
Date: 2016-06-02 01:59:10
Message-ID: CAB7nPqRTEEqd3xCJ9NffWhcpgeKEi6-i6UxGSJfosbXhJedE_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jun 2, 2016 at 10:04 AM, 德哥 <digoal(at)126(dot)com> wrote:
> Because I see EDB's document ECPGplus can parser #ifdef.
> so why postgresql community not do that?

Because EDB's stuff is not community stuff. I am not sure you can
expect both things to match, and it is not like ifdef grammar is not
supported as already mentioned by Michael.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-06-02 07:42:35 Re: BUG #14171: Wrong FSM file after switching hot standby to master
Previous Message 德哥 2016-06-02 01:04:21 Re: BUG #14167: ecpg parser cann't ignore code in #ifdef ?