From 20a1ef91f27dc3676a2983527365e35a6c5ae642 Mon Sep 17 00:00:00 2001 From: Ivan Date: Fri, 10 Jul 2015 01:43:09 +0300 Subject: [PATCH] Updated Coding Style (markdown) --- Coding-Style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Coding-Style.md b/Coding-Style.md index d7403c8..fea18d4 100644 --- a/Coding-Style.md +++ b/Coding-Style.md @@ -23,7 +23,7 @@ We recommend to follow these guidelines when writing code for RPCS3. They aren't * Use `s8`, `s16`, `s32`, `s64` for integral signed types. * Use `u8`, `u16`, `u32`, `u64` for unsigned types. * Use `float`, `double` for floating point numbers. - * Use `bool` as is; `char` for representing UTF-8 string character. + * Use `b8` for `bool`; `char` for representing UTF-8 string character. * Don't use `be_t<>` in function arguments/results, they are already little-endian. * But don't forget that dereferencing vm::ptr for PS3 leads to big-endian values. * Use `vm::ptr<>` arguments instead of `pointers`.