Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
snaiks-study [2016/05/25 14:10] karl [Goals] |
snaiks-study [2017/04/04 06:45] (aktuell) karl [Any-Type Inputs/Outputs] |
||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | ====== Snaiks ====== | + | ====== Snaiks |
**Signals and Systems from KiCad to C++** | **Signals and Systems from KiCad to C++** | ||
{{ :: | {{ :: | ||
- | 7.4.2016 | + | 7.4.2016\\ |
+ | For Updates please see [[Snaiks]] | ||
---- | ---- | ||
Zeile 17: | Zeile 18: | ||
The C++ classes are based heavily on templates, so most of the components can be used either for floating point or for integer calculations. | The C++ classes are based heavily on templates, so most of the components can be used either for floating point or for integer calculations. | ||
- | ==== Goals ==== | + | ===== Goals ===== |
* Generate beautiful C++ code from a KiCad schematic | * Generate beautiful C++ code from a KiCad schematic | ||
* Compiles without dynamic memory allocation (embedded, savety) | * Compiles without dynamic memory allocation (embedded, savety) | ||
Zeile 122: | Zeile 123: | ||
+ | ==== Any-Type Inputs/ | ||
+ | Perhaps it would be useful, that not all inputs must have the same type. For example a mute gate, where the enable is bool and the signal is double. | ||
+ | Pros: | ||
+ | * more flexible systems | ||
+ | Cons: | ||
+ | * every pin must have a type specified in KiCad (could be done with net-annotators, | ||
+ | * we cannot use a simple template-interface class any more, such as the SnsHybrid or SnsNumeric. | ||
+ | === Proposal === | ||
+ | * in cases, where this is really needed, a specific C++ class could be implemented | ||
+ | * mixture of numbers and bool shouldn' | ||
+ | |||
+ | {{tag> |