Do you always use unique names for class members?
Documentation here lists the kinds of members a class definition may contain. In summary:
- Parameters
- Methods
- Properties
- Class queries
- XData blocks
- Projections
- (and some that are relevant only for persistent classes):
- Storage definitions
- Indices
- Foreign keys
- SQL triggers
Later in the same document, a section headed "Class Member Names" contains this warning:
So I'm interested to hear how other DC members handle this.
- Do you comply (or at least attempt to comply) with this?
- If so, do you use any tools or naming conventions to assist you?
- Have you ever encountered "unexpected results" that were caused by a failure to comply?