Table of Contents

The purpose of this page is just to serve as todo or scratch pad for the development project and to list and share some ideas.

The code development project mentioned on this page has been finished by now. Chances are that this page is considerably outdated and irrelevant. The notes here might not reflect the current state of the code, and you should not use this as serious documentation.

Checkconfig

Implement function checkconfig that checks the consistency of cfgs, similar to checkdata for data structure.

Objectives

Implement function checkconfig that checks consistency of cfgs:

  1. For the user: input cfgs should be adjusted when necessary and possible, and feedback (warning/error) should be given when required options are missing or when forbidden or deprecated options are used. This should replace the current 'backward compatibility' code.
  2. Internal use: checkconfig should control the relevant cfg options that are being passed on to other functions.
  3. Output: only relevant cfg fields should be contained in the output (data.cfg), e.g. it should not contain unused default settings.

Relevant functions

Overview of relevant functions (where checkconfig should be implemented):


Overview of existing relevant functions:

Step 1

Add the check (objective 1) to the existing functions.


Required: check whether required options are present, give error when missing


Renamed: change old options/values into new ones + give warning


Deprecated: give warning when deprecated options are used


Forbidden: give error when forbidden option is used

Step 2

Incorporate existing functions in checkconfig:

Step 3

Control the output cfg:


trackconfig:


checksize: