Jim, In v15 I frequently use something like: OB SET($obj;\ k some key; "the value";\ k another key; "another value")
And so on. This also worked with Canon's OBJ module: OBJ_SET_TEXT($obj;k some dot notation key;"text to set") where: k some dot notation key = "a.b.c" In v17 to do that using native dot notation you would have: $obj[k some key]:="the value" $obj[k another key]:="another value" There isn't a direct equivalent for using dot notation the way we do using the OBJ module. This isn't really a problem I suppose I'm just not as comfortable with it. Yet, anyway. It may prove to be a good way to go but I suspect it's a little bit slower than directly referencing the object especially if you get several levels deep or are looping a large collection. $obj[k level 1].[k level 2].[k level 3]:="the value" At this point the code is becoming pretty unreadable. At least difficult to debug. I feels like it's not going to be the best solution but it's mainly a personal preference at this point. It seems like overloading the code with a lot of error checking that would best be done another way. On Wed, Oct 3, 2018 at 10:38 AM Jim Dorrance via 4D_Tech < [email protected]> wrote: > Why are constants less useful? If the value is equal to the constant, it > avoids potential upper/lower case problems, no? > -- 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] **********************************************************************
