Exercise solutions for The C Programming Language, 2nd edition
You will find sometimes a file named lorem_ipsum.txt (or similar) that you can use for testing.
For example, if a.out is the executable then you could do something like ./a.out < lorem_ipsum.txt.
This program uses the math library functions sin, exp and pow; make sure you link with the math library, e.g. gcc calculator.c -lm.
You can test the program like this ./a.out < lines.txt. lines.txt is a long computer science poetry.
You can time it like so time ./a.out < lines.txt.
Similar to 5-7, but you'll find two files; one for testing detab and one for entab.
Similar to 5-7.
You can test by giving the getword.c program itself as input: ./a.out < getword.c
You can use a long Computer Science poem as input for test: ./a.out < cs_poetry.txt (or the source code as in 6-1)
You can test by giving the source code as input: ./a.out < preprocessor.c
You can test with the text file as input: ./a.out tolower < lines.txt (or toupper for upper case conversion)
I opted for a little unusual solution. The result is only displayed when requested via the character 'p' (print).
You can use one or all the three files for testing: file1.txt, file2.txt, file3.txt
You'll find two Computer Science poems in the folder.
You can use the lorem_ipsum.txt file and compare the system's cat with this program.
Using bit fields results in a larger source code size; bit fields operations are more explicit. Compiled code size was equal on my architecture. The run time for the code using bit fields was slower.
You can use the time program on for timing and test, e.g. /usr/bin/time a.out. (The file lorem_ipsum.txt is read in the program.)
The program reads the file lorem_ipsum.txt and creates a file name result.txt.
The program opens the file lorem_ipsum.txt, uses fseek to fast forward close to the end of file and prints the content until the end of file.