> This sort of code exists in over 1,000 programs And has been repeated ad nauseam, implementing this purely as an interface to other programs is acceptable (and unavoidable in the short term). But that has ABSOLUTELY NOTHING to do with how each app functions internally.
> So all of that code would have to be rewritten > if we made the FullName/Date readyonly I don't think anyone suggested that solution. The set() implementation can parse the long string into the real, internal fields with ease. The real objection here isn't that you've got read/write properties for firstname/surname/fullname. The objection is that this is stored internally in a single buffer. That's it. The external interface of any of these "classes" (or apps or whatever) can be just the same as you expect. Just change the internal implementation (in a way that is, in the first place, probably easier than your buffer) and everyone will be happy. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
