C++ API for JSONiq

[Chris Hillery]

To at least include punching new store::Item methods through the zorba::Item API.

[Chris Hillery (ceejatec)]

I believe all necessary work has been done on the JSONiq branch already: at least the methods isJSONItem(), getJSONItemKind(), getObjectPairs(), getArrayMembers(), getObjectValue(), getArrayMember(), getPairName(), and getPairValue() are exposed on zorba::Item. Some of these methods may need to be changed/renamed/revisited depending on the final decision about whether "pairs" are a first-class type or not.

[Chris Hillery (ceejatec)]

Indeed the internal store API has not been updated to reflect the latest JSONiq spec; it still has methods for dealing with pairs and still has a "pair" Item. The public Zorba API reflects some of the same issues. According to Markos it is not intended that the internal store API will be corrected anytime soon.

On the conf call on 4/18/2012, we decided that for 2.5, I will simply remove the public API methods that reference pairs, leaving the API incomplete but at least not incorrect. Based on that, I have removed the methods getObjectPairs(), getObjectValue(), getPairName(), and getPairValue().

However, include/zorba/store_consts.h has an enum JSONItemKind which is used both internally and externally. One of the values in this enum is "jsonPair". This cannot be removed without fixing the internal store API.

[Chris Hillery (ceejatec)]

Edit to above: I have not removed getObjectValue() as it does not actually do anything with pairs. I have updated the documentation for this method to make it more clear. I did also have to remove one existing JSONiq test case.

[Chris Hillery (ceejatec)]

The "wrong" external C++ methods have been removed. Once Ghislain changes the store implementation internally to get rid of pairs, we should revisit the public API and see if any item-level methods should be made part of the public API.

And don't forget to remove jsonPair from enum JSONItemKind!