Re: [BUGS] BUG #14776: ecpg 4.12.0 issues with macros containing linecontinued blocks - Mailing list pgsql-bugs

From Thomas S. Chin
Subject Re: [BUGS] BUG #14776: ecpg 4.12.0 issues with macros containing linecontinued blocks
Date
Msg-id 11863a5c-d6f6-43c1-2c44-64a4f83722c4@genx.net
Whole thread Raw
In response to Re: [BUGS] BUG #14776: ecpg 4.12.0 issues with macros containing linecontinued blocks  (Michael Meskes <meskes@postgresql.org>)
Responses Re: [BUGS] BUG #14776: ecpg 4.12.0 issues with macros containingline continued blocks  (Michael Meskes <meskes@postgresql.org>)
List pgsql-bugs
Hello Michael,

Yes, I can. I had hit the "Save" button prematurely, expecting another
page to provide code fragments.

---

typedef char test_t[3];

EXEC SQL TYPE test_t IS VARCHAR[2];

// COMMENT OUT macros with line continued code block to get working
#define TEST_MACROS(x) { \       }

EXEC SQL BEGIN DECLARE SECTION;
test_t test;
EXEC SQL END DECLARE SECTION;

---

ecpg -o test.c test.pgc
test.pgc:10: ERROR: unrecognized data type name "test_t"

---

This test case works with ecpg (PostgreSQL 9.4.7) 4.10.0.
This test case works with ecpg (PostgreSQL 9.5.7) 4.11.0.
This test case does not work with ecpg (PostgreSQL 9.6.3) 4.12.0.

The code is processed successfully if the macros is omitted, commented
out or changed to be on a single line:
#define TEST_MACROS(x) { }

Thanks!

Best,
Thomas S. Chin


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
Next
From: "Augustine, Jobin"
Date:
Subject: Re: [HACKERS] [BUGS] Replication to Postgres 10 on Windows is broken