This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.
<!DOCTYPE html>
<htmlxmlns="http://www.w3.org/1999/xhtml"><head><title>CFrontend (infer.ClangFrontend.CFrontend)</title><linkrel="stylesheet"href="../../../odoc.css"/><metacharset="utf-8"/><metaname="generator"content="odoc 1.5.1"/><metaname="viewport"content="width=device-width,initial-scale=1.0"/><scriptsrc="../../../highlight.pack.js"></script><script>hljs.initHighlightingOnLoad();</script></head><body><divclass="content"><header><nav><ahref="../index.html">Up</a>–<ahref="../../index.html">infer</a>»<ahref="../index.html">ClangFrontend</a>» CFrontend</nav><h1>Module <code>ClangFrontend.CFrontend</code></h1></header><dl><dtclass="spec value"id="val-do_source_file"><ahref="#val-do_source_file"class="anchor"></a><code><spanclass="keyword">val</span> do_source_file : <ahref="../CFrontend_config/index.html#type-translation_unit_context">CFrontend_config.translation_unit_context</a><span>-></span><ahref="../../ATDGenerated/Clang_ast_t/index.html#type-decl">ATDGenerated.Clang_ast_t.decl</a><span>-></span> unit</code></dt><dd><p>Translate one file into a cfg. Create a tenv, cg and cfg file for a source file given its ast in json format. Translate the json file into a cfg by adding all the type and class declarations to the tenv, adding all the functions and methods declarations as procdescs to the cfg, and adding the control flow graph of all the code of those functions and methods to the cfg.</p></dd></dl></div></body></html>
