For example, if you want to represent any type of 4D variable in an object, each property ($oValue below) is an object with the (1) the type, and (2) the value OR the index of the value in the blob array. So if I pass a pointer to store a text property, it might be simply
OB SET($oValue;"type";Is Text";"value";$pValue->) If the value is a 2D array or other non-simple type, I append it to the blob array (using VARIABLE TO BLOB) and then the value is something like OB SET($oValue;"type";2D Array";"index";$lastIndex) This provides a way to serialize and unserialize every 4D type using an object manifest. The blob array and object manifest can be reduced to a single (blob) value by putting the object in element 0 of the blob array and then using VARIABLE TO BLOB on the blob array. This makes it easy to store or send over the network as a message. John DeSoi, Ph.D. > On Aug 1, 2017, at 9:12 AM, Chip Scheide <[email protected]> wrote: > > care to expand on this? > > I do not understand this part: >> arbitrary data are referenced by a number in the JSON, >> which is the element number for the BLOB array. ********************************************************************** 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] **********************************************************************
