> On 2/10/2016, at 8:00 am, Olivier Deschanels wrote: >> So, informal poll - who’s using objects for parameter passing ? > > Me ! And I’ve change all my approach of the code development thanks to the > objects. It’s so easy and it’s really efficient, especially if you want > polymorphe parameters. > I’ve replace in my own framework dozen of variables or arrays by a little > number of object. It’s a dream for trace and debug…
I use 4D objects a lot, but don’t use them very much for passing parameters - yet. I’ve been following this discussion (in its different guises) with interest. Several people have said that passing a 4D object as a parameter is easy to debug. Using 4D v15.2, I think I must be missing some new feature of 4D as I don’t understand how you can easily trace and/or debug an object when - only the first small part of the object is visible in the debugger? - a Design search cannot show the methods flow that use a particular parameter? I’m not for or against the idea - just trying to understand the enthusiasm for hiding parameters. I do understand how using an object will easily allow a large and variable number of “variables” to be passed to the server and back for an "Execute on server” function, and the calling/receiving methods should know what they are handling so that shouldn’t be a problem. But for general use, I’m trying to see an advantage… Cheers, Keith ********************************************************************** 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] **********************************************************************
