Re: BUG #8611: ECPG: unclosed comment "/*"

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Meskes <meskes(at)postgresql(dot)org>, alexsav23(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8611: ECPG: unclosed comment "/*"
Date: 2013-11-25 08:37:55
Message-ID: 20131125083755.GC16770@feivel.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Nov 24, 2013 at 09:53:29PM -0500, Stephen Frost wrote:
> I tend to agree with Tom here but I feel like I'm missing something-
> will this only make things "work" which would fail previously..? We

Yes, that's the way I see it.

> certainly don't want to risk breaking things for existing users, but
> perhaps it's not possible to have existing code which works and this is
> only 'loosening' of what we accept.

We're not exactly loosening but we aligning with what the C compiler accepts,
if that makes any sense.

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message jonathan.camile 2013-11-25 10:27:40 BUG #8629: Strange resultset when using CTE or a subselect
Previous Message Michael Meskes 2013-11-25 08:36:44 Re: BUG #8611: ECPG: unclosed comment "/*"