Re: BUG #8611: ECPG: unclosed comment "/*" - Mailing list pgsql-bugs

From Stephen Frost
Subject Re: BUG #8611: ECPG: unclosed comment "/*"
Date
Msg-id 20131125025329.GC17272@tamriel.snowman.net
Whole thread Raw
In response to Re: BUG #8611: ECPG: unclosed comment "/*"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #8611: ECPG: unclosed comment "/*"  (Michael Meskes <meskes@postgresql.org>)
List pgsql-bugs
Michael, Tom,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Michael Meskes <meskes@postgresql.org> writes:
> > Well, I think we can in ecpg as ecpg knows whether it's parsing C code =
or SQL
> > code.=20

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
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.

    Thanks,

        Stephen

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #8611: ECPG: unclosed comment "/*"
Next
From: Ronan Dunklau
Date:
Subject: Re: Server may segfault when using slices on int2vector