From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Frost <sfrost@mail.snowman.net>
To: BIONDI Philippe <Philippe.BIONDI@enst-bretagne.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: line size on C sources files
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-ID: <Pine.LNX.4.05.10003281345110.5831-100000@ns.snowman.net>
References: <Pine.SOL.4.10.10003281528160.16843-100000@ossian.enst-bretagne.fr>
X-SW-Source: 2000-q1/msg00417.html
Message-ID: <20000401000000.5HRp0kF0NRdT0h2kvuOehrwrpCtqNlD-waIz7HoV7H4@z>

On Tue, 28 Mar 2000, BIONDI Philippe wrote:

> On Tue, 28 Mar 2000, Stephen Frost wrote:
> 
> > 	Hrm, sounds like 'esqlc' is badly coded, yes, but I would question if
> > you actually *need* to have a 255+ line. :)
> 
> What about me wanting to expand macros before using esqlc (to use some
> macros in EXEC SQL sections) ? I don't control the size of my
> auto-generated C-SQL code. The question is : is this C-SQL code valid ? 
> You and I think it is. The answer of the support is "put backslashes".

	Hmm, well, what is true for C may or may not be exactly true for
SQL.  It may be that SQL has some silly limit on the number of characters
a SQL command can be on a single line.  If that is the case, then I see
little to do about it but to just use the backslashes.

		Stephen