Do you see anything wrong with programme ?

[Spiros Bousbouras]

I got the following programme from an old post:
http://tinyurl.com/53oa6o

It was given at a job interview and the question was
"The following program works, but what is a
potential problem with it? "

#include <stdio.h>
#include <stdlib.h>

int main() {
char buf[128];
FILE *fp = fopen(__FILE__, "r");

if (!fp) return EXIT_FAILURE;
while(!feof(fp)) {
if (fgets(buf, sizeof buf, fp))
puts(buf);
}
fclose(fp);
return 0;
}

My opinion follows below but you might want
to think about it before scrolling down.







The only problem I see with it is that it
might insert some extra newlines relative
to the original file. If the output of the
programme is meant to be recompiled
this might create problems. Otherwise
it seems fine to me.

Am I missing something ?

[Eric Sosman]

Spiros Bousbouras wrote:

I got the following programme from an old post:
http://tinyurl.com/53oa6o

It was given at a job interview and the question was
"The following program works, but what is a
potential problem with it? "

#include <stdio.h>
#include <stdlib.h>

int main() {
char buf[128];
FILE *fp = fopen(__FILE__, "r");

if (!fp) return EXIT_FAILURE;
while(!feof(fp)) {
if (fgets(buf, sizeof buf, fp))
puts(buf);
}
fclose(fp);
return 0;
}

My opinion follows below but you might want
to think about it before scrolling down.

[...]

The only problem I see with it is that it
might insert some extra newlines relative
to the original file. If the output of the
programme is meant to be recompiled
this might create problems. Otherwise
it seems fine to me.

Am I missing something ?

A statement of what the program is supposed to do?
We can see what it actually does, and we're told that it
"works," but without knowing what it is supposed to do
how can we tell if there's a "potential problem?" For
example, maybe it's *intended* to split long lines.

The only other things I notice is that the program
tries to keep going after an input error and that it
doesn't check for output errors -- but if these behaviors
are part of the specification, they're not "problems."

--
Er*********@sun.com

[Richard Tobin]

In article <d0**********************************@a23g2000hsc. googlegroups.com>,
Spiros Bousbouras <sp****@gmail.comwrote:

>It was given at a job interview and the question was
"The following program works, but what is a
potential problem with it? "

#include <stdio.h>
#include <stdlib.h>

int main() {
char buf[128];
FILE *fp = fopen(__FILE__, "r");

if (!fp) return EXIT_FAILURE;
while(!feof(fp)) {
if (fgets(buf, sizeof buf, fp))
puts(buf);
}
fclose(fp);
return 0;
}

>The only problem I see with it is that it
might insert some extra newlines relative
to the original file.

It certainly inserts a blank line between every line, and others if
any line exceeds the buffer size (which they don't if you're reading
this file, but see below). fgets() goes more naturally with fputs(),
and if you're not interpreting the text as lines it makes more sense
to use fread() and fwrite().
A more drastic problem is that __FILE__ is not guaranteed to refer
to the right file at run-time. If the source has been deleted, or
you're in a different directory, it's not going to work. It might
even refer to a completely different file.

-- Richard
--
:wq

[David Resnick]

On May 15, 10:46 am, Spiros Bousbouras <[e-mail]:

I got the following programme from an old post:http://tinyurl.com/53oa6o

It was given at a job interview and the question was
"The following program works, but what is a
potential problem with it? "

#include <stdio.h>
#include <stdlib.h>

int main() {
char buf[128];
FILE *fp = fopen(__FILE__, "r");

if (!fp) return EXIT_FAILURE;
while(!feof(fp)) {
if (fgets(buf, sizeof buf, fp))
puts(buf);
}
fclose(fp);
return 0;

}

My opinion follows below but you might want
to think about it before scrolling down.

The only problem I see with it is that it
might insert some extra newlines relative
to the original file. If the output of the
programme is meant to be recompiled
this might create problems. Otherwise
it seems fine to me.

Am I missing something ?

I don't do much file IO stuff, but fgets returns NULL on error. Is it
possible for it to return NULL but not set end of file? If so,
infinite loop...

And yes, puts will double the number of newlines. And lines longer
than
buf (not in that source, but could be) will be broken into pieces.
Seems
like printf is called for here...

-David

[Richard Tobin]

In article <fb**********************************@k37g2000hsf. googlegroups.com>,
David Resnick <ln********@gmail.comwrote:

>I don't do much file IO stuff, but fgets returns NULL on error. Is it
possible for it to return NULL but not set end of file?

Yes, if it gets an i/o error instead.

>If so, infinite loop...

That depends on the nature of the error. I don't think the standard
says anything about whether future reads may succeed after a error,
or what they should read (e.g. should they retry to read the same
block of a file?).

-- Richard
--
:wq