1 / 9

Translating Coded Programs into Executable Code

This document provides an overview of how coded programs are translated into executable code through interpreters and compilers. It discusses the inefficiencies of interpreters compared to compilers and the advantages of using a combination of both. The role of assemblers in converting assembly language to machine code is explored along with the importance of documentation in source code. Additionally, the debugging process is detailed, including types of errors such as syntax and logic errors, and the use of temporary print statements for error detection.

mac
Télécharger la présentation

Translating Coded Programs into Executable Code

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Translating Coded Programs into Executable Code • Disadvantage: -Work less efficiently than compilers and interpreted programs run more slowly because translate each program statement into machine language just before executing and must repeat each statement many times • Some programming language include both an interpreter and a compiler which are free- errors program and saving the object module to avoid repeating process

  2. Translating Coded Programs into Executable Code 3.Assemblers: -Converts assembly language statements into machine language. -Works like a compiler, producing a stored object module. -Assembly language is used almost exclusively by professional programmers to writ efficient code for specific type of computer.

  3. Documentation • Documented Source Code: The source code should implement the Logic illustrated by the program Design specification including comments to make it understandable and easy to update

  4. PRELIMINARY DEBUGGING PRINT as PRNT or putting a required comma or semicolonin the wrong place. The debugging process. Errors are typically classified as syntax errors or logic errors. Examples: Syntax errors: misspelling

  5. Logic errors (execution-time errors): writing an incorrect formula, or wrongly defined the problem.

  6. Temporary dummy print statements : print statements temporarily inserted into the code to help locate the error.

  7. Most compilers today include built-in debugging tools. • Color-code comments, command statements, and variables to assist readability. • Allow the programmer to choose between line-by-line execution and full-speed execution, among other features. This “execute, check, and correct” process is repeated until the program is free of bugs.

  8. CIS 10 Conclusion

More Related