aboutsummaryrefslogtreecommitdiff
path: root/1-11_word-count.c
diff options
context:
space:
mode:
authorzlg <zlg@zlg.space>2013-02-13 20:48:44 -0600
committerzlg <zlg@zlg.space>2013-02-13 20:48:44 -0600
commit5018e06c580dd21c958ec1672c26a3448faf0c55 (patch)
treecebbb56dad0a6b821cad3712c7977f6f9b0086ab /1-11_word-count.c
parentFix 1-09's solution (diff)
downloadknr-5018e06c580dd21c958ec1672c26a3448faf0c55.tar.gz
knr-5018e06c580dd21c958ec1672c26a3448faf0c55.tar.bz2
knr-5018e06c580dd21c958ec1672c26a3448faf0c55.tar.xz
knr-5018e06c580dd21c958ec1672c26a3448faf0c55.zip
Add license file, reorganize project
Diffstat (limited to '1-11_word-count.c')
-rw-r--r--1-11_word-count.c37
1 files changed, 0 insertions, 37 deletions
diff --git a/1-11_word-count.c b/1-11_word-count.c
deleted file mode 100644
index 1b4056c..0000000
--- a/1-11_word-count.c
+++ /dev/null
@@ -1,37 +0,0 @@
-#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;
-}