3 These are features that have been requested, and have been considered,
4 but are not yet implemented, because I'm undecided about how or whether they
5 should be implemented, and/or because they are difficult and/or time-consuming
8 Also, some of these features tend to push libconfig toward becoming a
9 general-purpose structured-data storage mechanism, which is really not the
10 intended purpose of this library. I think something like sqlite is better
11 suited for that sort of thing.
14 * Add an option for safe type conversions; that is, report an error
15 rather than silently truncating out-of-range values to 0 (namely int64 ->
19 * Add support for copying settings from one configuration to another. Need a
20 recursive function to copy a setting and call itself on all child settings.
23 * Add a += operator, so that additional elements can be appended to a list or
24 array. The issue with this is defining a consistent syntax. For example:
29 Should this result in ( 1, 2, 3, 4, 5 ), or ( 1, 2, 3, ( 4, 5 ))? I believe
30 it should be the latter. However, only the former makes sense for arrays.
33 * Add the ability to insert/delete elements at any position in a list or
34 array. A simple implementation would be expensive (shift all the elements
35 by one for every insert/delete), and a more efficient implementation would
36 add a lot of complexity to the library.
39 * Add limited support for preserving comments?
42 * Add support for unicode strings? A bit problematic, since flex doesn't
43 support unicode input, AFAICT. But maybe supply convenience functions to
44 convert between parsed UTF-8 strings and std::wstring.