From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Pavel PaJaSoft Janousek <janousek(at)fonet(dot)cz> |
Cc: | PgSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: [INTERFACES] Comment in ECPG - again |
Date: | 1999-04-22 15:53:40 |
Message-ID: | 19990422175340.A948@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Thu, Apr 22, 1999 at 10:06:07AM +0200, Pavel PaJaSoft Janousek wrote:
> But why ECPG know '//' and '/*' and '*/' C/C++ style comments?
// is also an SQL comment. The backend will parse it correctly too.
/* ... */ was added for convenience. After all this is C code. But #include
is CPP code.
> Somebody wrote, that ECPG translate only exec sql commands, not true,
> when I write this:
> //exec sql ssss
This is not an exec sql command, but a comment.
> So, is ECPG only ESQL compiler (translator) or complex translator from
> ESQL to C/C++? I think, that ECPG want be complex translator => it may know
> also preprocesor directives....
Please do not mix C/C++ with CPP. After all all CPP commands do not belong
into the C language at all.
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael(dot)Meskes(at)gmx(dot)net | Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Margarita Barvinok | 1999-04-22 16:16:42 | Re: [INTERFACES] ecpg cursors and scope |
Previous Message | Michael Meskes | 1999-04-22 15:50:17 | Re: [INTERFACES] ecpg cursors and scope |