Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Naming conventions again........
Message
From
28/08/1999 00:10:36
 
 
To
27/08/1999 16:29:01
Charlie Schreiner
Myers and Stauffer Consulting
Topeka, Kansas, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00258085
Message ID:
00258760
Views:
18
Hi Charlie ----

>I like polymorphistic names, so I think MS erred by naming things like PageCount, FormCount, ButtonCount. It's a PageFrame! It has a count! The property should be Count. If something has a Name, I call it Name, not CustName. It's in the Customer table, so that's the context.

I personally agree with the customer table argument, but several server database design tools would disagree.

OTOH, it's PageCount, FormCount, etc. because it's a reference to a collection of the root object, NOT the root object itself. Therefore, PageFrame.Count would be non-sensical. Is this a count of PageFrames? Is this the Count number for this PageFrame? And what about objects that hold multiple collections...they can't all be Count, can they?
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform