16 lines
676 B
Markdown
16 lines
676 B
Markdown
|
The code responsible for traversing all files/folders needs to be seperate from the actual code responsible for checksumming the files/folders. The return value still has to be fixated, but I would choose something like a string array/vector of filepaths.
|
||
|
|
|
||
|
|
Only use classes were it actually makes sense. Instead prefer structs for data encapsulation.
|
||
|
|
|
||
|
|
It needs to be able to accept cmdline arguments as input only. Args are comprised of:
|
||
|
|
|
||
|
|
- flags like --help or -v/--verbose
|
||
|
|
- a filepath from which it should checksum
|
||
|
|
|
||
|
|
It needs be able to checksum files or folders or both.
|
||
|
|
|
||
|
|
It should be able to save the checksums in a structured way. Something like:
|
||
|
|
|
||
|
|
- Database
|
||
|
|
- CSV
|
||
|
|
- ...
|