I could possibly agree with this if objects were more powerful and complete, but in the current implementation it just invites mistakes and maintenance issues. Object property names are just strings. Unless you build your own system where every property is an object that can provide meta-data, you can't even determine the type of the property. 4D objects are not self-describing as in other object systems. Having variables (and parameters) allows type checking and cross referencing to understand where things are used in the code base. If I have 100 instances of "name" as a property in my code, there is no way to safely make a change to that if I only want it to impact a subset of my objects.
If you could declare constants in code without restarting 4D, it might change my mind. John DeSoi, Ph.D. > On Sep 14, 2016, at 6:44 PM, David Adams <[email protected]> wrote: > > 1) Ignore process and IP variables. Period. (In fact, I'd recommend this no > matter what - mingling variables this way is kind of a crappy way to code > anyway.) > > 2) Make your payload one parameter, and make that JSON. (Real JSON that any > language can parse.) ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
