Homework 7: C Introductory Lab 2

EXERCISE 1: Write a program guess.c that picks a random number between 1 and 100 and has the user repeatedly guess the number in a while loop. For random numbers, use the random function. Here is a sample usage:

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

...
unsigned int seed;
scanf("%u", &seed);
srandom(seed);
//srandom((unsigned int)time(NULL));
int rand_num = random()%100 + 1;

Note that with the above approach, you'll produce the same random number every time you run your program, based on the seed. That's good, as it allows our testing code to work reliably. That said, I've shown commented code above that you can use just for fun that lets you pull the random number seed from the system clock, rather than based on user input.

A run of your program might look like this:

Enter a random seed: 112233
Guess a number: 50
Too high!
Guess a number: 37
Too low!
Guess a number: 43
Too high!
Guess a number: 40
Too high!
Guess a number: 39
Correct! Total guesses = 5

You can take a look at the tests to see how we're checking your work. In particular, it's important that you say "Too high!", "Too low!", and "Total guesses = " followed by the number of total guesses. Additionally, it's important that the seed is the first thing requested from the user, followed by the guesses.

If a user guesses a number that is not between 1 and 100, tell them it's out of range and do not include that guess in the count of total guesses.

You can declare an array in C by giving the type and size of the array. See arrays.c for a sample program.

Just like in Java, C has arrays that allow you to have a sequence of values. You can allocate space on the stack or in the heap. Here's an example of the difference:

int array_stack[10];//Allocates a 10 integer array on the stack
int *array_heap = malloc(sizeof(int)*10); //Allocates a 10 integer array on the heap

In either case, you can use [] notation or derefencing to read and write elements:

array_stack[3] = 5; //equivalent to: *(array_stack + 3) = 5;

Unlike Java, there's no reasonable way to find out the length of an array, so you need to keep track of an array's length yourself. And if you write past the end of an array, there's no check or "out of bounds error" - it will just modify whatever happens to be next in memory!

In arrays.c, the following line is commented out:

array[10] = 5;

Uncomment that line, and observe how the value of x changes. Note that clang issues a warning that you're doing a bad thing, which you are, but the program should still run. What does this imply about the layout of the variables in memory? After you've experimented, re-comment out this line to get rid of the compiler warning.

EXERCISE 2: Create a new file sums.c to ask the user how many numbers they'd like to store and what number they'd like to start at. Allocate an array to store that number of numbers, and write that number of numbers into the array, consecutively and starting at the number they say they'd like to start at. Then, print out the sum of the numbers at odd indices in the array.

Here's an example of me interacting with my program:

How many numbers do you want to include? 4
What number do you want to start at? 7

C does not have classes or objects. However, you'll often run into situations where you want to group related values together. For this purpose, you can create a struct, a special kind of user-defined type.

Structs are defined using the keyword struct, a name for the struct, and a list of member variables within curly braces. For example, here's a struct to represent a student (see student.c for the full code listing):

struct Student {
    char *first_name;
    char *last_name;
    int id;
};

You can create an instance of a struct type by declaring it with the struct keyword, and access member variables using the dot (.) operator. See student.c for details.

EXERCISE 4: Create a new file complex.c. In this file, add a struct type struct Complex containing two doubles representing the real and imaginary parts of a complex number. Add a function, multiply_in_place that has two parameters, both pointers to variables of type struct Complex. After this function is run, the two input pointers should reference the product of the two complex numbers they originally pointed to. multiply_in_place should not return anything (i.e., its return type is void). Note that if you have two complex numbers \(c_1\) and \(c_2\) whose real parts are \(a_1\) and \(a_2\) and whose imaginary parts are \(b_1\) and \(b_2\), respectively, then the real part of their product is \(a_1 * a_2 - b_1 * b_2\), and their imaginary part is \(a_1 * b_2 + a_2 * b_1\).

In main, the program should prompt the user for the two complex numbers and then print out both numbers before and after calling the multiplication function. Here is a sample run, which you should match to make sure you pass the tests:

Enter real part of c1: 2
Enter imaginary part of c1: 5
Enter real part of c2: 3
Enter imaginary part of c2: 4
Before multiplication:
c1:       2.00 +       5.00 i
c2:       3.00 +       4.00 i
After multiplication:
c1:     -14.00 +      23.00 i
c2:     -14.00 +      23.00 i

To get the output looking like I did with two decimal places, I wrote a short function for printing a complex number:

/* Prints a complex number with two decimal places of precision */
void print_complex(struct Complex num) {
  printf("%10.2f + %10.2f i\n", num.real, num.imaginary);
}

Please copy and paste this function into your code and use it to allow you to match my output exactly.

Note for testing scripts: The scripts won't directly check that your multiply_in_place function is working in the manner stated here, with the values that are pointed to by the inputs actually being changed. However, we will consider not doing this to be an instance of hyper-tailoring your code to our tests. One way to ensure that you are not doing so is to make sure you call print_complex on a variable c1 twice and on a variable c2 twice, with the only non-printing thing that happens in between being a call to multiply_in_place.

Note that while the testing scripts are ignoring your spacing, they are checking for exact matches on the colons/etc that I have above.