From 48843306e2ea51b95525a0a5f04d2afac3193176 Mon Sep 17 00:00:00 2001 From: lizzie Date: Fri, 7 Nov 2025 16:50:03 +0100 Subject: [compat] Fix other DragonFlyBSD/NixOS issues (#2860) Uh - the other pr that had "Fix dragonfly" got commits lost and I didn't notice... oops; cherry picked them back through :) Signed-off-by: lizzie Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/2860 Reviewed-by: crueter Reviewed-by: MaranBr Co-authored-by: lizzie Co-committed-by: lizzie --- docs/Coding.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'docs/Coding.md') diff --git a/docs/Coding.md b/docs/Coding.md index ec524cbbf8..8d02df4088 100644 --- a/docs/Coding.md +++ b/docs/Coding.md @@ -8,6 +8,8 @@ But for new developers you may find that following these guidelines will make ev Simply put, types/classes are named as `PascalCase`, same for methods and functions like `AddElement`. Variables are named `like_this_snake_case` and constants are `IN_SCREAMING_CASE`. +Except for Qt MOC where `functionName` is preferred. + Template typenames prefer short names like `T`, `I`, `U`, if a longer name is required either `Iterator` or `perform_action` are fine as well. Macros must always be in `SCREAMING_CASE`. Do not use short letter macros as systems like Solaris will conflict with them; a good rule of thumb is >5 characters per macro - i.e `THIS_MACRO_IS_GOOD`, `AND_ALSO_THIS_ONE`. -- cgit v1.2.3