From dc9fdc99edd552d0cbe3323d6e96509dde9f5b7c Mon Sep 17 00:00:00 2001 From: Ivan Date: Fri, 10 Jul 2015 01:47:31 +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 fea18d4..1e774f7 100644 --- a/Coding-Style.md +++ b/Coding-Style.md @@ -22,7 +22,7 @@ We recommend to follow these guidelines when writing code for RPCS3. They aren't * Use only limited number of types in function arguments and result type. * 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 `float`, `double` for floating point numbers. `f32` and `f64` are also available, but not widely used. * 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.