Server : Apache/2.4.41 (Ubuntu) System : Linux absol.cf 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory :  /usr/share/doc/libconfig9/

Upload File : current_dir [ Writeable ] document_root [ Writeable ]

TO-DOs:

These are features that have been requested, and have been considered,
but are not yet implemented, because I'm undecided about how or whether they
should be implemented, and/or because they are difficult and/or time-consuming
to implement.

Also, some of these features tend to push libconfig toward becoming a
general-purpose structured-data storage mechanism, which is really not the
intended purpose of this library. I think something like sqlite is better
suited for that sort of thing.


* Add an option for safe type conversions; that is, report an error
  rather than silently truncating out-of-range values to 0 (namely int64 ->
  int).


* Add support for copying settings from one configuration to another. Need a
  recursive function to copy a setting and call itself on all child settings.


* Add a += operator, so that additional elements can be appended to a list or
  array. The issue with this is defining a consistent syntax. For example:

  x = ( 1, 2, 3 );
  x += ( 4, 5 );

  Should this result in ( 1, 2, 3, 4, 5 ), or ( 1, 2, 3, ( 4, 5 ))? I believe
  it should be the latter. However, only the former makes sense for arrays.


* Add the ability to insert/delete elements at any position in a list or
  array. A simple implementation would be expensive (shift all the elements
  by one for every insert/delete), and a more efficient implementation would
  add a lot of complexity to the library.


* Add limited support for preserving comments?


* Add support for unicode strings? A bit problematic, since flex doesn't
  support unicode input, AFAICT. But maybe supply convenience functions to
  convert between parsed UTF-8 strings and std::wstring.