|Did you know ...||Search Documentation:|
|Integration of strings and dicts in the libraries|
While lacking proper string support and dicts when designed, many predicates and libraries use interfaces that must be classified as suboptimal. Changing these interfaces is likely to break much more code than the changes described in this chapter. This section discusses some of these issues. Roughly, there are two cases. There where key-value associations or text is required as input, we can facilitate the new features by overloading the accepted types. Interfaces that produce text or key-value associations as their output however must make a choice. We plan to resolve that using either options that specify the desired output or provide an alternative library.
System predicates and predicates based on library
process dicts as an alternative to traditional option lists.
Some predicates now produce structured data using compound terms and access predicates. We consider migrating these to dicts. Below is a tentative list of candidates. Portable code should use the provided access predicates and not rely on the term representation.
The XML representation could benefit significantly from the new features. In due time we plan to provide an set of alternative predicates and options to existing predicates that can be used to exploit the new types. We propose the following changes to the data representation:
element(Name, Attributes, Content)will become a dict.
The JSON representation could benefit significantly from the new features. In due time we plan to provide an set of alternative predicates and options to existing predicates that can be used to exploit the new types. We propose the following changes to the data representation:
json(KeyValueList), the new interface will translate JSON objects to a dict. The type of this dict will be
nullwill be represented as atoms.
The HTTP library and related data structures would profit from
exploiting dicts. Below is a list of data structures that might be
affected by future changes. Code can be made more robust by using the
library functions for extracting values from these structures.