diff options
author | zlg <zlg@zlg.space> | 2013-02-07 02:52:52 -0600 |
---|---|---|
committer | zlg <zlg@zlg.space> | 2013-02-07 02:52:52 -0600 |
commit | 9ff9f305ff7059681d691d750582e6259cd90b59 (patch) | |
tree | e715b7954f93cd217d3f3f59fdfb029596085b20 /1-11_word-count.c | |
parent | Fix style issue and correct 1-24 (diff) | |
download | knr-9ff9f305ff7059681d691d750582e6259cd90b59.tar.gz knr-9ff9f305ff7059681d691d750582e6259cd90b59.tar.bz2 knr-9ff9f305ff7059681d691d750582e6259cd90b59.tar.xz knr-9ff9f305ff7059681d691d750582e6259cd90b59.zip |
Solve Exercises 1-1 to 1-12
It was bugging me and the exercises are simple, so I pumped'em out.
Diffstat (limited to '')
-rw-r--r-- | 1-11_word-count.c | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/1-11_word-count.c b/1-11_word-count.c new file mode 100644 index 0000000..1b4056c --- /dev/null +++ b/1-11_word-count.c @@ -0,0 +1,37 @@ +#include <stdio.h> + +/* The C Programming Language, 2nd Edition + * + * Exercise 1-11: How would you test the word count program? What kinds of + * input are most likely to uncover bugs if there are any? + * + * Answer: New lines (such as those caused by wrapping text) are most likely to + * introduce erroneous word counts, as well as symbols that are strung together + * but don't create actual words. + */ + +#define IN 1 +#define OUT 0 + +int main(void) { + int c, nl, nw, nc, state; + state = OUT; + nl = nw = nc = 0; + + while ((c = getchar()) != EOF) { + nc++; + if (c == '\n') { + nl++; + } + if (c == ' ' || c == '\n' || c == '\t') { + state = OUT; + } else if (state == OUT) { + state = IN; + nw++; + } + } + + printf("%d %d %d\n", nl, nw, nc); + + return 0; +} |