line size on C sources files

line size on C sources files

[BIONDI Philippe]

Hi all,
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 ?
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)

best regards, Phil.

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

Re: line size on C sources files

[Stephen Frost]

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

Re: line size on C sources files

[BIONDI Philippe]

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

Re: line size on C sources files

[Stephen Frost]

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

Re: line size on C sources files

[BIONDI Philippe]

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

That is not a sufficient reason to trunc my C lines. I don't mind about
the sql ones (in which TAILLE_TAMPON becomes 25) but about C lines in
which errno becomes longer stuff, or CELL_VALUE(x,y) which expands to 
lines that break the 255 limit.

If the C code is correct, the esqlc is broken, and the solution of the
support is not a solution.

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

Re: line size on C sources files

[Martin v. Loewis]

> 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

Re: line size on C sources files

[Bill C Riemers]

Of course, just because the language allows very long lines, does not mean
you should use them.  If for no other reasons than they make it very difficult
to read your code.  Even if you have automatic line wrapping in the editor
you view the code with, if you want to debug the code, the line numbers you
can specify in gdb or any other debugger won't reflect wrapping that is not
in the source code itself.

			Bill

Re: line size on C sources files

[BIONDI Philippe]

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

line size on C sources files

[BIONDI Philippe]

Hi all,
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 ?
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)

best regards, Phil.

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

Re: line size on C sources files

[Stephen Frost]

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

Re: line size on C sources files

[Bill C Riemers]

Of course, just because the language allows very long lines, does not mean
you should use them.  If for no other reasons than they make it very difficult
to read your code.  Even if you have automatic line wrapping in the editor
you view the code with, if you want to debug the code, the line numbers you
can specify in gdb or any other debugger won't reflect wrapping that is not
in the source code itself.

			Bill

Re: line size on C sources files

[BIONDI Philippe]

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

That is not a sufficient reason to trunc my C lines. I don't mind about
the sql ones (in which TAILLE_TAMPON becomes 25) but about C lines in
which errno becomes longer stuff, or CELL_VALUE(x,y) which expands to 
lines that break the 255 limit.

If the C code is correct, the esqlc is broken, and the solution of the
support is not a solution.

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

Re: line size on C sources files

[Martin v. Loewis]

> 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

Re: line size on C sources files

[Stephen Frost]

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