I<Name> is a little weird at first (unless you used to work for Microsoft) and i don't generally do any "hungarian" at all these days, but this one little notational "deviation" allows a few nice things (and you can take it or leave it):
- interfaces can be rapidly found with control-shift-t in eclipse by typing "i" - resolves naming conflicts with annotations and classes without compromises - code reads faster and more clearly because it makes functionality immediately clear (you know when you can implement without seeing the class definition so you can see the design better) while it wasn't the most popular decision (and believe me, i do see both sides of the issue because naming is very important to me when coding), it does have some modest benefits and at the least (to me, anyway) it's simply not an important issue. six of one. half dozen of the other. you do get used to it. Curtis Cooley-2 wrote: > > Eyal Golan wrote: >> Actually it is. Thanks. >> I want to show it to some friends whom are learning with me a course in >> OOD. >> >> > Hopefully whoever is teaching the course will provide a better way to > name interfaces than starting them all with I :( > > > > Confidential/Privileged information may be contained in this email. If you > are not the intended recipient, please do not copy, distribute or use it > for any purpose, nor disclose its contents to any other person. Please > notify the sender immediately if you receive this in error. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- View this message in context: http://www.nabble.com/UML-Diagram-of-Wicket-structure-tp21354861p21358642.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
