Page 98 of 229 Start Back Next End ZBasic Language Reference 88 ZBasic Microcontrollers byte-by-byte comparison of the content of two structures. If one or more members of the structure are the BoundedString type, the byte-by-byte comparision may result in a False value even though the strings are identical. This is because the currently-unused portion of the string store may contain byte values that are different between the two instances being compared. Similarly, comparison of structures containing allocated strings, while allowed, is not recommended because of the likelihood of resulting in false negatives. Structures may contain members that are sub-byte types, Bit and Nibble. Members that are Bit type will be aligned on the next available bit boundary and those that are Nibble type will be aligned on the next available nibble boundary. If a member that is not a sub-byte type follows a sub-byte type member, that non-sub-byte member will be aligned on the next available byte boundary. Depending on how you define your structure, this may result in “holes” in the structure layout representing unused bits. The unused bits are generally of no consequence but it is important to note that these “holes” may interfere with the equality/inequality test for structures that are not initialized because the unused bits will have an indeterminate value. You can avoid this potential problem by performing a block initialization on locally defined structures. Example ' this structure contains a "hole", unused bits following the ab member Structure foo Dim b as Byte Dim ab(1 to 4) as Bit Dim b2 as Byte End Structure Sub Main() ' this structure is not automatically initialized Dim bar as foo ' this call zeroes out the entire structure Call MemSet(bar.DataAddress, SizeOf(bar), 0) ' other code follows End Sub Another method of creating a user-defined type, compatible with VB6, is also supported. The syntax for a Type definition is: [Public | Private] Type <name> <member-definition> ... End Type In this case, the <member-definition> is the same as for defining a member of a Structure except that the visibility attribute (Public, Private, or Dim) is not allowed. The visibility of each member will be the same as the visibility of the Type itself. BasicX Compatibility Note Structure and Type definitions are not allowed in BasicX compatibility mode. 3.25.1 Structures in Persistent Memory and Program Memory Structures in Persistent Memory and Program Memory may be defined using the syntax: {Public | Private | Dim} <name> As Persistent <type>