2014:generative_c_visualizing_code
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2014:generative_c_visualizing_code [2013/11/07 07:38] – created jonjagger | 2014:generative_c_visualizing_code [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Back to [[conference: | Back to [[conference: | ||
| \\ | \\ | ||
| - | **Title**: | + | **Title**:Generative C++: Visualizing Code\\ |
| **Proposer**: | **Proposer**: | ||
| **Proposer**: | **Proposer**: | ||
| Line 7: | Line 7: | ||
| **Duration**: | **Duration**: | ||
| **Description**: | **Description**: | ||
| + | The code you work on is often a complex mass; never is the documentation a true reflection of the code. Existing brown field work is almost void of any engineering diagrams that reflect the composition of the code base.\\ | ||
| \\ | \\ | ||
| + | Using clang as a source code analyser it is easy to generate diagrams via technologies such as graphviz, XMI, gnuplot, or even Visio! | ||
| + | \\ | ||
| + | We show you how to use clang to generate detailed:\\ | ||
| + | Entity relationship diagrams.\\ | ||
| + | Sequence diagrams.\\ | ||
| + | Dependency diagrams.\\ | ||
| + | \\ | ||
| + | But you can also generate diagrams that don't really have a formal name but are useful to you, from tracking the lifetime of a message object in a multithreaded application through to analysing the evolution of that object in source control history. | ||
| \\ | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
| - | |||
2014/generative_c_visualizing_code.1383809902.txt.gz · Last modified: 2016/06/11 14:05 (external edit)