From 733b71c293a18b957563632331fe758344c7cb9c Mon Sep 17 00:00:00 2001 From: Margen67 Date: Fri, 7 May 2021 23:38:39 -1000 Subject: [PATCH] Remove whitespace, https --- Code-Formatting-Guidelines.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Code-Formatting-Guidelines.md b/Code-Formatting-Guidelines.md index 60bb4e1..b1f0218 100644 --- a/Code-Formatting-Guidelines.md +++ b/Code-Formatting-Guidelines.md @@ -68,5 +68,4 @@ While modern compilers like to tout that the compiler should be left to decide f While PCSX2 willfully makes no promise to retain backwards support for savestates, it is none the less a convenience for developer, tester, and user alike when we do. So when possible it is recommended that programmers making changes to the savestate code (normally denoted as a Freeze() function) be sure to increment the savestate version in Savestate.h and, if you know how, implement backward support for the old version (if not, then simply increment the savestate version and let someone else fix the backwards compatibility in a later revision). This allows PCSX2 to at the very least fail gracefully when encountering an unknown savestate, and ideally it allows for another coder familiar with the system to properly implement backwards compatibility with the older savestate revision. - [1]: http://en.wikipedia.org/wiki/Hungarian_notation - \ No newline at end of file + [1]: https://en.wikipedia.org/wiki/Hungarian_notation