47e0a1656e
In the future, NAND filesystem access will be limited to one IOS instance, for safety reasons and to make it possible to consider supporting NAND images. This means that any code accessing the NAND filesystem must go through the FS device, both for code that is external to IOS and internal. Because we don't want to introduce any singleton, this requires internal IOS code that needs NAND access to be part of an IOS device class, so they can access the FS device easily. Making some of the internal ES implementation functions member functions also prevents them from being (mis)used outside of IOS, since they cannot be called everywhere anymore. |
||
|---|---|---|
| .. | ||
| Android | ||
| Core | ||
| DSPSpy | ||
| DSPTool | ||
| PCH | ||
| UnitTests | ||
| VSProps | ||
| .clang-format | ||
| CMakeLists.txt | ||
| dolphin-emu.sln | ||