public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: BIONDI Philippe <Philippe.BIONDI@enst-bretagne.fr>
To: Stephen Frost <sfrost@mail.snowman.net>
Cc: BIONDI Philippe <Philippe.BIONDI@enst-bretagne.fr>, gcc-help@gcc.gnu.org
Subject: Re: line size on C sources files
Date: Tue, 28 Mar 2000 05:36:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10003281528160.16843-100000@ossian.enst-bretagne.fr> (raw)
In-Reply-To: <Pine.LNX.4.05.10003281329120.5831-100000@ns.snowman.net>

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".

(Well I must also say about the support that I spend 3 hours to explain
them the two first lines of my mail. But that is another story ! :))


--
Philippe Biondi
Systems administrator
Webmotion Inc.
http://www.webmotion.com
mailto:philippe.biondi@webmotion.com
Fax. (613) 260-9545

WARNING: multiple messages have this Message-ID
From: BIONDI Philippe <Philippe.BIONDI@enst-bretagne.fr>
To: Stephen Frost <sfrost@mail.snowman.net>
Cc: BIONDI Philippe <Philippe.BIONDI@enst-bretagne.fr>, gcc-help@gcc.gnu.org
Subject: Re: line size on C sources files
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10003281528160.16843-100000@ossian.enst-bretagne.fr> (raw)
Message-ID: <20000401000000.CrmeiEVr8N0noZFBTa7Hw_oxArMOKwziXXmkdliEmZE@z> (raw)
In-Reply-To: <Pine.LNX.4.05.10003281329120.5831-100000@ns.snowman.net>

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".

(Well I must also say about the support that I spend 3 hours to explain
them the two first lines of my mail. But that is another story ! :))


--
Philippe Biondi
Systems administrator
Webmotion Inc.
http://www.webmotion.com
mailto:philippe.biondi@webmotion.com
Fax. (613) 260-9545

  reply	other threads:[~2000-03-28  5:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28  5:19 BIONDI Philippe
2000-03-28  5:25 ` Stephen Frost
2000-03-28  5:36   ` BIONDI Philippe [this message]
2000-03-28  5:41     ` Stephen Frost
2000-03-28  6:34       ` BIONDI Philippe
2000-04-01  0:00         ` BIONDI Philippe
2000-04-01  0:00       ` Stephen Frost
2000-04-01  0:00     ` BIONDI Philippe
2000-04-01  0:00   ` Stephen Frost
2000-03-28 15:14 ` Martin v. Loewis
2000-03-28 21:16   ` Bill C Riemers
2000-04-01  0:00     ` Bill C Riemers
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` BIONDI Philippe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SOL.4.10.10003281528160.16843-100000@ossian.enst-bretagne.fr \
    --to=philippe.biondi@enst-bretagne.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=sfrost@mail.snowman.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).