public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: 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: <200003282305.BAA01319@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.Ovf5uw-rSRYqml_A9I5Gaj8WwDnaQA1a456lpXP2HSc@z> (raw)
In-Reply-To: <Pine.SOL.4.10.10003281510400.16843-100000@ossian.enst-bretagne.fr>

> 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 ?

There is no such rule, but there is a different rule saying that all
implementations of C can have arbitrary limits, as long as they are
documented as such. However, for a number of limits, minimum
acceptable implementation limits are given, in particular, as per
5.2.4.1 (of C99)

- 4095 characters in a logical source line

So if you have more characters than that in a line, an implementation
of standard C could reject it and still claim conformance to the C
standard. Of course, no implementation of C is *required* to reject
it, in fact, implementations are encouraged to avoid imposing fixed
translation limits whenever possible.

Please note that this number is from C99; it may have been lower in
C89.

Regards,
Martin

  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
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 [this message]
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=200003282305.BAA01319@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --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).