CPSC 421-010 Object-Oriented Programming (OOP) Spring 2025

Week 5 Class 10 Thu Feb 13 Posted: Feb 13

After Class

• President's Day Observance Tuesday, Feb 18 University open, no classes

• Due Dates Exercises due next week ordered by due date:

  • ✓ Exercise 29: Scope Crossword Due: Monday, Feb 17
  • ✓ Exercise 31: Grouping Functions Crossword Due: Monday, Feb 17
  • ✓ Exercise 32: Sequence Diagram Due: Tuesday, Feb 18
  • Exercise 30: Utilities Due: Wednesday, Feb 19

  Each exercise is due by 4:30 pm on the day indicated.

• Exercise 30: Utilities

  For each @TODO you are to declare a single function declaration, and only call it once in the example. Do not solve any of the @TODOs with two or more functions, or call the function more than once.

Announcements

• Project 2

  I am introducing Project 2 because we do not have class on Tuesday, Feb 18.

Agenda

• Notes: Scope
• Exercise 29: Scope Crossword Due: Monday, Feb 17

• Exercise 30: Utilities Due: Wednesday, Feb 19

  Provide a single function declaration in the file Utilities.hpp and a single function call in UtilitiesExamples.cpp for each @TODO in UtilitiesExamples.cpp. Once you do, remove the @TODO for that block. The function declarations in Utilities.hpp must follow the order of the examples of the call in UtilitiesExamples.cpp.

  Do not implement the function. Do not provide a function definition. Only provide the declaration and example single call using the variables given. The function declaration must be complete enough so that it would be possible to implement the function.

  Make sure the program compiles. But, since you are not providing a function definition, the program will not link or run successfully.

  To compile the program without linking:

  For each function declaration, include a Doxygen comment that describes the function and describes what data is IN, OUT, or IN/OUT. An example is already in the include file. Note that Doxygen comments start with /**.

  Finish the problem for each @TODO, remove the @TODO, and then commit. Each commit should complete one @TODO. The first one is completed as an example.

  If any of the following occur, then the entire exercise score is a 0:

  • Function definitions
  • Does not compile (expected to not link)
  • Object files, e.g., UtilitiesExamples.o, in the repository
  • Additional includes
  • Any code changes besides adding function declarations and implementing @TODOs
  • Use of any other files
  • Use of C++ standard library functions
  • Use of templates
• Notes: Grouping Functions
• Exercise 31: Grouping Functions Crossword Due: Monday, Feb 17
• Notes: Sequence Diagrams

• Exercise 32: Sequence Diagram Due: Tuesday, Feb 18

  Create a sequence diagram at SequenceDiagram.org for the diagram on the right, which is for parsing a start tag with an attribute.

  Start with the SVG file with the GitHub Classroom Repository link at Brightspace, and commit your changes to that repository.

  Your final result should look exactly like the image shown here.

  Make sure to save as a SVG Image File (vector image with embedded source text)