Thank you for your interesting question and feedback on the documentation section of ADOxx. We are continously updating and enhancing the documentation pages and appreciate community feedback.

With respect to the map "concept" in ADOxx, please find below a detailled summary of the functionality provided by this data structure

1. Create a new empty map using AdoScriptA key and a related value are separated by a colon (":"), multiple key-value pairs are separated by comma (","), the set of pairs is enclosed in curly parentheses ("{" and "}").#
Important remark: As the colon character (":") is used for defining maps, a key (if of type string) must not contain such a character. If this is not respected, ADOxx will display an error message. Minding the colon character is especially relevant, if not fixed, but dynamic keys are used (e.g. object names).

2. Create/Initialize a map with key/value paris
3. Get the map length using m.length or LEN (m)
Length (size) of a map. m has to be of type map. The result is number of elements of m. Alternatively, LEN m can be used
4. Check on empty map using m.empty
Returns 1 (true) if the map is empty and 0 (false) otherwise.
5. Remove map item by key using merase(m, k)The return of merase is the value of the deleted entry

6. Add item to map using subscription
7. Retrieve value by key
Subscription to a map using SUB or []
m SUB k or m, where m has to be of type map, k of type string, integer, real, measure or time. The result is the element of m with key k. If the key is not contained in the map, the result is of type undefined.
Value elements of a map, and so the result of the subscription, may be of any type. The type of two different value elements of one map needs not to be the same. Use type() if you are not sure about a value element's type.
8. Application of above concepts to realize a keyset iterator (assuming integer keys)Please be aware that the above approach assumes integer keys and uses the ADOxx array concept to store the keyset. The functionality can be globally added to your implementation by adding an AdoScript FUNCTION

In addition to the above functionality, additional functionality is planned for an upcoming ADOxx platform release.

Dear Wilfrid,

thank you very much for the detailed description. Since I'm to lazy to always copy and adapt the code to get the "keyset iterator" I have implemented 2 functions that should do this for me.

The attached .asc file contains the functions as well as some comments with the details. I have tested the code a bit, but not extensively. Since they follow your solution for the determining the keyset they do not allow for "," or ":" in the keys or the values.
mapKeySet(myMap) - returns an array containing all the keys. It uses their correct type (i.e. integer keys are integers in the array and string keys are strings in the array).
mapKeySetStrings(myMap) - returns an "@" separated list (string) containing all the keys. This one works ONLY for maps where all the keys are strings. Because of that the entries in the list are also strings and not further encoded.

There is also a third function, that however seems to have a problem:
mapKeySet2(myMap) - returns an "@" separated list (string) containing all the keys. The entries in the list are stored to reflect their type (e.g. strings are surounded by ").
The function itself seems to work fine, however when I split the list into it's tokens and pass a token to the "eval(...)" function I get an asleo-84 error, but after that I apparently still the right value.

Best regards,
Patrik

Attachments:

mapKeySetFunctions.asc (4.5k)