Re: Segmentation Fault.... C99F

On Thu, 12 Apr 2007, Richard Heathfield wrote:

Tak-Shing Chan said:

<snip>

I was demonstrating that your ``reason for avoiding //
comments'' is flawed.

No, you weren't. You were merely pointing out that on some occasions //
comments do not line-wrap. This was already known, so you have provided
no new information.

If you honestly cannot see where I am heading, I think I will give up.

I haven't a clue where you're heading. Your call.

Let me repost the bits that you have snipped:

``[...] Long lines are the culprit, not
// comments. Take any C program. Mechanically wrap them at 20
characters. I bet that the majority of them will fail to
compile, even if you use /* comments */.''

Let me expand on this a little bit:

(1) To begin with, if we set our newsreaders to be narrower
than the Usenet convention (67 characters), then we should not
copy-and-paste from a post and expect the results to be
compilable. Why? By forcing a mechanical rewrap, we risk
breaking identifiers (or string literals) in the middle. This is
particularly common with long printf lines.

(2) If original posters obey the Usenet line length
conventions, then our line lengths would match (or exceed)
theirs, so // comments would not and could not cause any
problems in the first place.

In other words, // is not the culprit.

Tak-Shing
.

Relevant Pages

  • Re: Segmentation Fault.... C99F
    ... Mechanically wrap them at 20 ... I bet that the majority of them will fail to ... Oh sure, and if you wrap them at zero characters, tehy'll disappear. ...
    (comp.lang.c)
  • Re: Danger of using FillMem() on a string? Speed of Abs()?
    ... The culprit here is the following: ... const to a PChar. ... ShowMessage() will not/cannot show any more characters after the null ... The characters in the string are still there, ...
    (comp.lang.pascal.delphi.misc)