Paul, You know it's perfectly acceptable to just not even worry about it. Personally I never wrote a SOAP API or client and it looks like I never will. :-)
If you don't need dot notation and don't see anything on the horizon that will require it spend that time doing other things. I've seen some implementations of objects and dot-notation that really did nothing useful except inject new techniques into a stable environment with no particular benefit. This reminds me of a former neighbor in our condo and I talking about some work that needed to be done to the property. We were going over the options and extent of the work. Not surprisingly I tended to want to make things perfect and last forever. He heard me out and simply said at his age, "it only has to last as long as I do." Whether that's short sighted or profound it's a perfectly valid point of view. On Fri, Oct 5, 2018 at 12:15 AM Paul Dennis via 4D_Tech < [email protected]> wrote: > I've been thinking about it more from the point of practicalities than the > coding. I understand how we can create documentation of the objects. My > problem is three years down the line when you revisit some old code written > by third-party. With tables and records and the structure it's relatively > straightforward to track through the code and work out what's going on. I > can see this being a real problem with objects. There just doesn't seem to > be any visibility. The data could be buried many layers down in an object > let alone all the quotes, dots and semi colons involved. I think my first > step is to have another eye test. > Paul > > -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
