Long Acronyms Should Be Pascal Cased

9 Comments

• Exactly what you do. I exclude the rule for constants.
  

• Pascal casing is used for exposed constants in the framework, e.g. double.MaxValue instead of double.MAX_VALUE, so I would recommend that you fix the FxCop violations. Remember that the constants listed will be exposed to any derived type, so they are part of your public API and you should make them consistent with the rest of the framework.
  

• What you also have to be aware of, is there is another FxCop rule (or maybe its just written) that says not to expose public constants. I think that one is a bit odd, but I ignore it to. This isn't a breaking change, it only affects readability.
  

• On a completely different note, it makes me shudder to see you storing a default date in a string.
  

• Anon, it's a log story. We store it as a string and a date to support an existing app that we must run in parallel with for a while.
  

• Kevin,
  
  
  
  "unless a field represents something that is truly constant, e.g. PI, then it could change in a future version. Clients will not be able to get such a change without being recompiled"
  
  
  
  Yes, this is why there is a rule that says not to expose public constants, because nothing is ever guaranteed not to change. I don't know where the rule is off the top of my head. It may not even be an FxCop rule, but its a good rule either way :)
  

• I agree with the notion of not exposing constants publicly, and instead wrapping them behind a static property or something similar.
  
  
  
  But in answer to the original question I use the uppercased, underlined format too
  
  
  
  private const int THIS_IS_MY_CONSTANT_AND_DONT_FORGET_IT=0; // :snicker:
  

• может у кого нить есть ещё информация по этому поводу??
  

• 50 % discounts on all airtickets flights and hotels as well as all football matches
  email us at makitelove@yahoo.com
  
  no advance payment needed