A year- and topic-organized archive of C++ exam questions, solution sources, class-design exercises, and review notes.
The repository preserves independent examination and practice problems rather than one application or reusable library. Annual folders may combine a Markdown problem statement, one standalone program, a multi-file class exercise, and local input data.
No package manager, common C++ standard, build system, test harness, or supported compiler is declared for the full collection.
The refreshed default-branch tree contains 113 files in 54 directories, including these verified formats:
| Format | Count | Role |
|---|---|---|
.cpp |
58 | Solutions and practice programs |
.h |
22 | Class and exercise-specific headers |
.md |
17 | Root multilingual docs, annual problem sets, and topic notes |
.dat |
7 | Program input fixtures |
.gif |
4 | Formula images embedded in particular annual questions |
.txt |
4 | Text input or notes |
.pdf |
1 | Exam material in the Southeast University collection |
The inventory is evidence of content, not a statement that every solution is correct or portable.
| Area | Representative topics |
|---|---|
| Procedural foundations | arrays, strings, numerical exercises, recursion, sorting, and file input/output |
| Classes and objects | constructors, destructors, composition, static members, and object arrays |
| C++ language features | templates, operator overloading, inheritance, virtual functions, and polymorphism |
| Data handling | date, employee, text-statistics, and local .dat/.txt exercises |
| Supplemental problems | palindrome detection, English-text statistics, numerical calculations, and common string functions |
Annual README files are the nearest available problem specifications. Read them before interpreting the adjacent source as a complete answer.
| Path | Contents and boundary |
|---|---|
2010/ to 2015/ |
Larger annual sets, including multi-file class-design problems |
2016/ to 2019/ |
Smaller sets covering text, dates, arrays, recursion, and strings |
计算机学院2019/ |
A separate 2019 Computer Science school problem set |
部分其他题目总结/ |
Standalone palindrome, text-statistics, and numerical examples |
常用函数总结/ |
Notes about commonly used string functions |
东南大学C++期末考试题/ |
Exam PDF, solution source, and data files |
A numbered problem directory is its own compilation boundary. Headers such as Date.*, Employee.*, Teacher.*, or shape classes do not form a repository-wide API.
Use a C++ compiler compatible with the selected source, but determine the required language level from that problem rather than from this README. The archive contains no compiler-version file, IDE project, Makefile, CMake configuration, or package manifest.
Some programs read local files such as file.txt, data.dat, date.txt, and s1.dat. Keep the working directory aligned with the problem folder and inspect every .cpp and .h before constructing a build command.
- Select one annual problem and read its local
README.mdplus every adjacent source and header. - Identify required input files, expected interactive input, output, and any file writes.
- Choose and record one compiler, language mode, and working directory for that problem only.
- Build in an isolated directory with synthetic input; do not omit a translation unit simply because another problem is single-file.
- Compare results with the written question, record uncertainty, and leave unrelated years unchanged.
There is no universal command because the source layout and required language features vary by year and question.
- Historical code may rely on compiler-specific functions, older headers, permissive conversions, or undefined behavior.
- Multi-file exercises can fail if a required implementation or header is omitted from the build.
- Programs using
.datand.txtfixtures may silently depend on the current working directory or modify those files. - Formula GIFs belong to specific questions and are not product screenshots or repository-wide illustrations.
- Existing problem statements include external-source references whose availability and reuse terms were not independently verified.
No repository-wide run, test, build, lint, or format command was found. None of the problems was compiled during this documentation audit, so no compiler or C++ version is claimed as supported.
For a code change, report the exact problem path, compiler, language mode, source list, input, and observed output. A passing result for one problem must not be presented as coverage for another year.
Keep changes scoped to one question or one clearly documented indexing correction. Preserve annual and Chinese paths, local fixtures, formula links, and original question text; avoid introducing shared helpers that alter the educational independence of the problems.
Keep English, Simplified Chinese, and Japanese READMEs aligned in section order, counts, paths, links, and compatibility statements.
No repository license file is present. Exam questions, external references, formula images, and solution code may have different origins. Confirm provenance and redistribution permission before reuse; a source link is attribution evidence, not automatically a license grant.
- HaoXiang Huang
- didadida1688@gmail.com
- Project homepage