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

Week 5 Class 9 Tue Feb 11 Posted: Feb 11

After Class

• The BUILD.md file contains instructions on turning TRACE on and off

Announcements

• Project 1
  • v1b Scores were added to Brightspace

  • v1c Issues posted in GitHub. Scores will be added to Brightspace later.

    Issues include:

    • Coding Practices Task List issue is still open
    • Missing n const
    • Missing n auto
    • Function comment does not follow style
    • Mention of srcfacts in refillContent files
    • Missing header comment in refillContent.hpp
    • Missing newline at EOF in refillContent.{hpp,cpp}
    • Missing success return
    • Mixed tab and space indentation
    • Multiple blank lines
    • Return in separate section for srcfacts.cpp
    • Unneeded include files in refillContent.hpp
    • Header comment in refillContent.{hpp,cpp} should not include the function comment
    • Include file refillContent.hpp is not self sufficient with clang
    • Insert blank line after filename in header comment in refillContent.{hpp,cpp}
    • Function declarations missing comments in refillContent.hpp
    • Function definitions missing comments in refillContent.cpp
    • Missing filename in header comment in refillContent.{hpp,cpp}

    I have some more feedback on the contents of comments, but they will not affect your score.

  • v1d and v1e Due dates extended.
  • Every function should have single purpose. Do not make a function try to be an Accessor::predicate and Mutator::command. Use separate functions for each.
  • If your xml_parser functions refer to srcML, srcFacts, or srcfacts concerns, then they violate the rule of none of these concerns in xml_parser. Specifically, if they contain expression counts or use srcML tags, such as "expr", then they violate a primary design rule for this project. Remove them immediately.
• Exercise 24: srcFacts Concerns Answers

Agenda

• Notes: Naming
• Exercise 26: Naming Crossword

• Notes: Method Naming Standards

  We will follow these naming standards in this course.

• Exercise 27: Method Naming Standards Crossword

• Exercise 28: TRACE

  Demonstrate the running of your program with TRACE on for a:

  • line comment
  • short block comment
  • Doxygen block comment

  You will have to create the srcML for each of these code examples. Use the srcML Playground. Keep the examples as short as possible (i.e., only include a comment). Download these files and have them ready before you start the screencast. Also before the screencast, build with the TRACE option on.

  The form to submit the asciinema link is in the title of this exercise.

  To make the output cleaner, redirect the generate table to a file ./srcfacts < FILENAME > report.md

• Notes: Event State
• Notes: Scope

Unless otherwise noted, exercises are due by 4:30 pm on Wed Feb 12