Proposal: use leading underscore for private field names

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Minor - P4
    • 1.4
    • Affects Version/s: 1.3.1
    • Component/s: None
    • None
    • None
    • Minor Change
    • None
    • None
    • None
    • None
    • None
    • None

      This proposal is to adopt the rather ugly convention of using leading underscores for field names.

      While this is not a very attractive convention, it seems like the least ugly way to avoid having property names that differ only in case from their underlying backing field names (which causes warnings when compiling with the CLSCompliant assembly attribute).

      We will allow a few weeks to go by to allow time for comments before deciding whether to do this or not.

              Assignee:
              Robert Stam
              Reporter:
              Robert Stam
              Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: