-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO.txt
30 lines (27 loc) · 1.27 KB
/
TODO.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
TPython already does almost all that I want to do :(
The rest is not worth the hassle.
My thoughts:
- make a class that hold configuration data.
- one can pass a string with python code which is then parsed into an internal dictionary.
- a python dictionary can be passed directly if it is available either from python or from
another C api program. The dictionary replaced the internal one.
- The calib object has move semantics like python objects. It is only needed to read from.
Deep copying is not possible.
- The object can be queried with a get(string) function. The result object has cast operators
to a number of standard calibration type objects like:
- ints
- double
- bools
- strings
- vector<int>
- vector<double>
- vector<bool>
- vector<string>
- another calib dict object
- The last kind would be the result of the key being found to be a dict.
- The result object would not be possible to be copied, stored, or assigned. This way one is
forced to cast it immediately.
- in all the class would be well suited to configure code that may be called both from C++ code
or from a python api, without having to pass down a lot of individual config options.
/Simon
all done :)