[banshee] HACKING: add one more rule, unnoticed until now
- From: Andrés Aragoneses <aaragoneses src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [banshee] HACKING: add one more rule, unnoticed until now
- Date: Wed, 9 Oct 2013 23:03:57 +0000 (UTC)
commit 6e7e6724207d4f6990d9e4c90fda871cb84324fb
Author: Andrés G. Aragoneses <knocte gmail com>
Date: Thu Oct 10 01:03:47 2013 +0200
HACKING: add one more rule, unnoticed until now
It turns out all the Banshee codebase has explicit accessors, even
if `private` is normally the default when there is no accessor.
This rule will deter people from using new MonoDevelop's SourceAnalysis
facilities (or Resharper in the case of VS.NET) to cleanup code in an
incorrect way.
HACKING | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
---
diff --git a/HACKING b/HACKING
index 9313b35..b623742 100644
--- a/HACKING
+++ b/HACKING
@@ -90,6 +90,9 @@ guidelines. If code is in violation, you will be asked to reformat it.
var compare = (a + b * c) != (d - e * f);
+ 12. Please write `private` accessors even if the language defaults
+ to it in the context you're in.
+
.NET API Naming Guidelines
==========================
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]