Current state

[Zehui-He]

The program is now able to remove any unnecessary tabs, spaces and new line characters from the Json file. The next step is making the parser accept non-nested numeric values.

[Zehui-He]

The program is now able to read nested json file with a very naive approach in terms of efficiency and memory consumption. No memory leak was detected by Valgrind. The next step is to reconstruct the JsonObj class.

[Zehui-He]

The JsonObj class is now separated from the JsonValue class and their circular dependency is resolved. The unordered_map underneath the JsonObj is encapsulated. More methods should be added to the JsonObj class to make it easier to use.

[Zehui-He]

The parsing function is rewritten. Different value types are now has its own parsing function(handler) and they can call each other recursively. The logic of the parsing function follows the ECMA-404 standard. However, the parsing of numeric value is not implemented yet. The separation of the logic also improves the maintainability of the program. The program is now able to handle some real-world JSON files.
The next stage of this project is to remove JsonValue::type. This is because the data type has the chance to be unsynchronized with the data type stored by JsonValue::data (for example, the user attempt to modify the underlying data). On the other hand, user has direct access to JsonValue::type also introduce vulnerability.