From: Michael Meskes <meskes@postgresql.org>
To: Pavel PaJaSoft Janousek <janousek@fonet.cz>
Cc: PgSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] Comment in ECPG - again
Date: Thu, 22 Apr 1999 17:53:40 +0200
Message-ID: <19990422175340.A948@gmx.net> (raw)
In-Reply-To: <001301be8c96$fbac2ae0$0200a8c0@server.fonet2.cz>
References: <001301be8c96$fbac2ae0$0200a8c0@server.fonet2.cz>
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.Meskes@gmx.net | Use PostgreSQL!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: meskes@postgresql.org, janousek@fonet.cz
Subject: Re: [INTERFACES] Comment in ECPG - again
In-Reply-To: <19990422175340.A948@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox