CBOLD Pros and Cons
|
| Pros |
Cons |
| CBOLD uses standard C++. |
You may need to learn some C++. |
| CBOLD parts are easily created with a text editor. |
CBOLD does not come with extensive part libraries. |
| CBOLD parts do not require specification of drive strengths (e.g., input, output, power, passive). |
CBOLD does not have an electrical rules checker.
For more information, see: Why does CBOLD Lack an Electrical Rules Checker? |
| CBOLD output is largely under the control of the user. |
CBOLD requires manual back-annotation.
For details, see Engineering Change Orders. |
| The CBOLD framework is free software. |
CBOLD requires a C++ compiler and an IDE (recommended). |
| Every time you run a CBOLD project, all output is generated. |
|
| You can extend CBOLD to generate any desired output. |
CBOLD does not come with support for all netlist formats. |
| CBOLD generates standard Xilinx® constraint (UCF) files. |
|
| A text-based design medium is conducive to integrating detailed notes within the design, e.g., in C++ comments distributed through the design's source code. |
|
