# Interpreting recovered code - DE Decompiler > DE Decompiler reconstructs Delphi-like program logic from native instructions and available metadata. The information retained in the binary determines the detail of the result. Canonical HTML: ## Interpreting recovered code DE Decompiler reconstructs Delphi-like program logic from native instructions and available metadata. The information retained in the binary determines the detail of the result. ### What the high-level listing represents Native-code decompilation recovers expressions, `if` conditions, `case` blocks, loops and calls, including recognized VCL methods. This makes program logic accessible for reverse engineering and security analysis. The listing reconstructs the implementation; it does not reproduce the original source text. ### Names, data structures and calls - **Variable names:** original local names are commonly absent from the binary. Generated identifiers represent the recovered values; analyst-assigned names can make their role clearer. - **Types and layouts:** RTTI supplies type information where it is available. Other structures may be inferred from access sizes and addresses, so field types, boundaries and signatures can need further interpretation. - **Calls:** recognized VCL methods can be shown by name. A call that cannot be identified may remain a method or address-based call without its original VCL name. - **Compiler variation:** compiler generations, libraries and optimization affect the emitted instructions and metadata. Version-specific RTTI knowledge helps interpret them, but an inferred type or expression can still need correction. ### Check significant conclusions 1. Identify the exact binary, unit, class and procedure under review. 2. Read the decompiled logic and declarations, using the native instructions to resolve uncertain expressions or types. 3. Examine callers, argument preparation, conditional branches and associated strings. 4. Use the HEX Editor when an instruction or recovered value needs to be checked against file data. 5. Record what was observed directly and what remains an inferred interpretation. ### Security investigation The recovered structure and code help forensic investigators, antivirus analysts and corporate security teams locate suspicious logic, potential backdoors and unwanted functionality. Establish how a value or call is used before drawing a conclusion. A string or API name alone does not establish malicious behavior or prove that a branch executed. ### Source recovery Recovered forms, declarations and procedure code can reduce manual recovery work. Native-code decompilation does not reproduce a compilable source project. Before opening exported code in an IDE, manually analyze and correct decompilation inaccuracies and incompatibilities, reconcile inferred types and unidentified calls, and provide missing units, components and dependencies. Building the recovered material requires that manual work. ### Applications built with C++Builder C++Builder-specific library RTTI knowledge bases are not yet available. Functions outside the shared VCL coverage, and object properties or methods that cannot be identified, may be shown without their library names. Code decompilation quality for C++Builder is therefore noticeably lower than for applications written in Delphi. This limitation concerns code-reconstruction quality and library-name recognition. The other supported features remain available for C++Builder under the same edition rules as for applications written in Delphi. C++Builder code is reconstructed as Delphi-like Pascal, with PAS/DFM output. It is not converted back into the original C++ source. As with other native-code reconstruction, review and correct inferred types, generated names and decompilation inaccuracies manually before using the recovered material in an IDE.