@@ -5,3 +5,10 @@ The qucs-gui code base is not easy to walk through.
...
@@ -5,3 +5,10 @@ The qucs-gui code base is not easy to walk through.
As I wanted to understand how it works, I started to "reverse engineer" it. My focus is on component definition, library management and how the netlist and the simulation commands are generated.
As I wanted to understand how it works, I started to "reverse engineer" it. My focus is on component definition, library management and how the netlist and the simulation commands are generated.
You will find in this document a somewhat detailed description of the [Component class](/1-Qucs-code-analysis/2.0-component-class), the [Qucs netlister code](/1-Qucs-code-analysis/3.1-Qucs-Netlister), and the specifics added for [Spice support](/1-Qucs-code-analysis/3.2-Spice-Netlister)
You will find in this document a somewhat detailed description of the [Component class](/1-Qucs-code-analysis/2.0-component-class), the [Qucs netlister code](/1-Qucs-code-analysis/3.1-Qucs-Netlister), and the specifics added for [Spice support](/1-Qucs-code-analysis/3.2-Spice-Netlister)
I have done these analyses using:
-[callgrind](http://valgrind.org/docs/manual/cl-manual.html) and [KCacheGrind](https://kcachegrind.github.io/html/Home.html)
