Thread: File problem

Originally Posted by zach

1. I am not showing measures to get rid of "new lines" because I removed the various shots I took at the problem, in order to show the code that was bugged.

That's good, but that also means we have no way of verifying what you did to try and remove the newlines.

Originally Posted by zach

2. "Lack of knowledge": I would have thought that was what this forum is all about.

That's targeted specifically to your comment that "The dangle issue in C seems a bigger problem than C itself." There's no point pre-judging a tool until you know how to use it.

Originally Posted by zach

3. How I know the new route is better? The old route used a global array with 0-s and 1-s, guiding which descriptions to show / not to show. I was told, not to use globals - bad style. Therefore I consider the new routine a better one.

Ah, I see. What I was curious about is how you got round this fgets+puts issue without actually solving the bug. The issue sounds orthogonal to the issue of a global array (i.e., what you described does sound like an improvement, but in a different though related area).

Originally Posted by zach

3. "These days" this seems to be a reference to my age.

It's a reference to the fact that man pages are older than the Web. I don't even know if you're older than Unix or younger than the Web (though since you've referred to previous programming experience I guess you're older than the iPhone )

Originally Posted by zach

I am surprised given the skewness of the points you raise.

What do you mean?

Originally Posted by zach

Laserlight, Hi, I suggest you take another look at the code. You might see how the line skips came about. Zach K.

I thought you said that there were no (unintended) line skips:

Originally Posted by zach

If that were the case there would be a line skipped after each intended line, which there isn't.