From 6ef591dfc6ee016f3faecd25da9e1b2d051ea9b4 Mon Sep 17 00:00:00 2001 From: Ivan Date: Thu, 29 Oct 2015 09:43:34 +0300 Subject: [PATCH] Newline at the end of file (new rule) --- Coding-Style.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Coding-Style.md b/Coding-Style.md index 2b2d00c..a6a2b3c 100644 --- a/Coding-Style.md +++ b/Coding-Style.md @@ -13,6 +13,7 @@ We recommend to follow these guidelines when writing code for RPCS3. They aren't * Comment *every* hack you do, *every* snippet you comment out and *every* improvable code. * If you have to comment or place a commented code snippet, include the reasons to do that in the comment. * Don't use `/**/` for commenting out multiple lines. Use `//` on every line instead. In Visual Studio, for example, you can just select desired lines and use `Ctrl+K,C` combination to comment every line with `//`, `Ctrl+K,U` reverts this. +* Ensure that the every source file you modify has the newline at the end of file. Every line ends with "newline" and the end of file must have "newline" too, GitHub usually warns about it. *** ### Emulator coding style