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 [thread overview]
Message-ID: <Pine.LNX.4.05.10003281329120.5831-100000@ns.snowman.net> (raw)
Message-ID: <20000401000000.Zwr5jOBIpR_AVVvvpztSl1nRKfXeFl00v2P0odceTsY@z> (raw)
In-Reply-To: <Pine.SOL.4.10.10003281510400.16843-100000@ossian.enst-bretagne.fr>
On Tue, 28 Mar 2000, BIONDI Philippe wrote:
> Is there anywhere on earth a rule/specification/usage that say that a C
> source file must not have any line that exceeds 255 characters ?
Not that I am aware of. C has always (to my knowledge) completely
ignored whitespace. gcc certainly doesn't appear to care.
> I remember when my TPascal 4 EDI complained about lines bigger than 128
> characters, but I don't know any rule that limit this size (neither posix,
> nor ansi..). Am I wrong ?
> Because if such rule exist, gcc cpp is wrong expanding macros on one
> (sometimes very long) line, and my Ingres precompiler win the round.
> If not, my convictions are right and esqlc is too badly coded ! (and I can
> complain to CAI)
Hrm, sounds like 'esqlc' is badly coded, yes, but I would question if
you actually *need* to have a 255+ line. :)
Stephen
next prev parent reply other threads:[~2000-04-01 0:00 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 [this message]
2000-03-28 5:36 ` BIONDI Philippe
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.LNX.4.05.10003281329120.5831-100000@ns.snowman.net \
--to=sfrost@mail.snowman.net \
--cc=Philippe.BIONDI@enst-bretagne.fr \
--cc=gcc-help@gcc.gnu.org \
/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).