Date: Mon, 16 Oct 2000 12:14:36 +0200
From: Michael Meskes <meskes@postgresql.org>
To: pgsql-interfaces@postgresql.org
Subject: Re: STRANGE ecpg OUTPUT
Message-ID: <20001016121436.A18767@feivel.credativ.de>
Mail-Followup-To: pgsql-interfaces@postgresql.org
References: <000d01c035ba$88008ae0$acd61d97@clibero.it>
	<20001016104113.A16958@feivel.credativ.de>
	<009d01c0374f$1bef8540$44d41d97@clibero.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <009d01c0374f$1bef8540$44d41d97@clibero.it>;
	from maurizio@dreamtech-it.com on Mon, Oct 16, 2000 at 10:57:26AM
	+0200

On Mon, Oct 16, 2000 at 10:57:26AM +0200, Maurizio wrote:
> test1.pgc is the sample program in interfaces/ecpg/test end has the CR at
> the end of the line. Also sqlca.h has the CR. I think the problem is in the
> parser. Do you know where in the sources of ecpg is the fput o fprintf to
> the test1.c?

Sure. But I doubt that that is were the problem resides. After all it does
not look as if the lines in question are the ones completely parsed, but
those that are only run through the lexer. 

In preproc/pgc.l some stuff is just ECHO'ed. I think this may be the one.
You could create a pgc.c containing debugging output and check from there. 
I'd recommend you start checking if your ECHO macro is correct though.

> If you try to see test1.c there are a 0x09 char and not a 0x0A at the end of
> the line.

Strange.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!