All submissions should clearly identify your name, the course number, the assignment number, and each problem worked. Since some homework submissions can be a bit lengthy (with your source code and program output included), please make it easy to find your answer -- consider using a highlighter pen, penciled-in brackets, handwritten labels, etc. Without exception, you should use a fixed-width font for all code listings so they can be scanned quickly by the TAs. If the TAs can't decipher your submission, they can't give you the credit you deserve.
You may collaborate with other students as you do your homework, but if you do, you must report who you collaborated with on your homework assignment. Downloading homework solutions from the internet or submitting the work of anyone else and representing it as your own will be treated as a violation of BYU's honor code.In short, solutions may exist to this and other assignments out there in netland, but don't go looking for them -- you're shortchanging your own education if you do, and it is easier to detect cheating than you might think.
For those of you unfamiliar with C, we've made it much easier to create code to test your answers on many problems by giving you some C code to start with. Often the links to this code will be given in the Clarifications section of each assignment. Always read this section carefully -- the information can save you a great deal of time!
For problem 2.59, you should write, compile, and run a C program that performs the requested operation on several different values of x and y. (It is always a good idea to test your code thoroughly.) You can find skeletal code to help test your solution here. With this problem and other homework problems, when using skeletal code provided, please turn in only that code you wrote with your submission.
Problem 2.61 is good preparation for the first lab. The whole point of the restricted coding rules is to get you thinking about things from a different perspective. You can find skeletal code to help write and test your solution here.
For Problem 2.71, you should use this code to test your solution. Make sure you understand why the original code fails, and make sure to test your code on a variety of different values of the word. (Just change the initialization in the C code and recompile.) You should include some results (output) in your submission, but you need only include the C source code for the new version of xbyte() (actually myxbyte()) that you create.