CSE 333 25su Exercise 8

out: Monday, July 14, 2025
due: Wednesday, July 16, 2025 10:00 am. No late exercises accepted.

Goals: Write a small procedural (no classes or objects) C++ program from scratch, learn the basics of C++ stream I/O, and learn to use the cpplint style checker for C++ code.

Description: Write a C++ program that:

• prompts the user for a positive integer (strictly >0, your code should check the input value and report an error if this is not true)
• prints out all integers that are factors of that integer with a newline at the end; feel free to used the simplest, brute-force factorization algorithm you can think of (hint: n%k==0), and you should print each factor only once, in ascending order. For example, if the user enters the number 100, the interaction with the terminal should look like:

  bash$ ./ex8
  
  Which positive integer would you like me to factorize? 100
  
  1 2 4 5 10 20 25 50 100
  
  bash$ 

  If you wish, the last output number can be followed by a blank space before the newline, although it's not needed.
• Uses std::cin to read from the terminal and std::cout to write to the terminal

---

Your code must:

• compile without errors or warnings on CSE Linux machines (lab workstations, attu, or CSE home VM)
• have no crashes, memory leaks, or memory errors on CSE linux machines (valgrind works on C++ programs just like it does for C programs)
• be contained in a single file called ex8.cc that compiles with the command g++ -Wall -g -std=c++17 -o ex8 ex8.cc -- do not submit a Makefile.
• be pretty: the formatting, modularization, variable and function names, and so on must make us smile rather than cry. If in doubt, follow the Google C++ Style Guide (linked from the course resources page). We suggest using the cpplint style checker, but without the --clint option, which is for C code.
  Note: cpplint warns about some issues that can be ignored for our purposes, although it is unlikely to report any for this exercise. Be sure that you understand any warnings that remain or other deviations from the Google C++ Style Guide and be able to explain why they do not present a problem. (And, yes, you may have a using namespace directive in your code if you don't want to write std:: everywhere for short exercises like this, even if cpplint complains about it. You can also use individual using std::... directives, which do conform to the style guide.) The class discussion group is a good place for questions and discussion about these issues.
• be robust: you should think about handling bogus input from the user (if any), and you should handle hard-to-handle cases (if there are any) gracefully.
• have a comment at the top of each source file with your name, and CSE or UW email address.

You should submit your exercise using the Gradescope dropbox linked on the course resources web page.