[Bullets] Compiled vs Interpreted Languages

  1. compiler is a computer program that transforms source code written in a programming language into another computer language, often in a binary form, that is understood by the computer platform.

  2. A compiler usually transforms a high-level programming language to machine code specific to a platform, so that it can then be directly executed in that platform.

  3. An interpreter is a computer program that directly executes instructions written in a programming or scripting language, without previously compiling them into a machine language program.

  4. Compiled languages uses a compiler to translate the source code to machine code specific to a platform, and then this compiled form is taken to any computer with that platform, and executed; compile once and execute as many times.

  5. Interpreted languages compiled line-by-line as as that line was about to be executed. 

  6. Performance was not the best with complete interpreted languages, as, if a loop or subroutine caused certain lines to be executed multiple times, they would be recompiled every time.

  7. Advantages of compiled approach

    1. We can have compile time type checking, that prevent type mismatch or syntax issues coming up during run time.

    2. We can have code optimizations during the compile time looking into whole code and run the optimized code during run time.

    3. The code will run faster as it is already compiled for a particular platform and can be directly executed without needing to have to do the translation every time.

  8. Disadvantage for the compiled approach: 

    1. Not Portable: The executable code generated after compilation is platform dependent and there should be a different executable for different platform.

      1. For such software, there need to be a different executable for every different platform (Windows, Linux, Mac etc).

  9. Advantages of interpreted approach

    1. Code is more portable, as the same program can be shipped to any platform. An interpreter specific to a platform may convert this code (or executable) line by line to that platform specific machine language and then execute.

  10. Disadvantages of interpreted approach

    1. There is no compile time type checking and actual issues might come up during run time.

    2. Compile time code optimizations are not possible. This is because, in interpreted approach, only one line of code is available at a time to the interpreter.

    3. The code will run slower as it is converted to machine language while executing.

  11. Examples

    1. C++ and Fortran are examples of compiler based languages.

    2. PHP and perl are examples of interpreter based languages.

  12. Newer programming languages like Java, Python etc. uses a combination of compiler and interpreter; a compiler may output some form of intermediate bytecode (Java's .class files or Python's .pyc files), which is then executed by a bytecode interpreter (Java Virtual Machine or Python virtual machine).



Quick Notes Finder Tags

Activities (1) advanced java (1) agile (3) App Servers (6) archived notes (2) Arrays (1) Best Practices (12) Best Practices (Design) (3) Best Practices (Java) (7) Best Practices (Java EE) (1) BigData (3) Chars & Encodings (6) coding problems (2) Collections (15) contests (3) Core Java (All) (55) course plan (2) Database (12) Design patterns (8) dev tools (3) downloads (2) eclipse (9) Essentials (1) examples (14) Exception (1) Exceptions (4) Exercise (1) exercises (6) Getting Started (18) Groovy (2) hadoop (4) hibernate (77) hibernate interview questions (6) History (1) Hot book (5) http monitoring (2) Inheritance (4) intellij (1) java 8 notes (4) Java 9 (1) Java Concepts (7) Java Core (9) java ee exercises (1) java ee interview questions (2) Java Elements (16) Java Environment (1) Java Features (4) java interview points (4) java interview questions (4) javajee initiatives (1) javajee thoughts (3) Java Performance (6) Java Programmer 1 (11) Java Programmer 2 (7) Javascript Frameworks (1) Java SE Professional (1) JPA 1 - Module (6) JPA 1 - Modules (1) JSP (1) Legacy Java (1) linked list (3) maven (1) Multithreading (16) NFR (1) No SQL (1) Object Oriented (9) OCPJP (4) OCPWCD (1) OOAD (3) Operators (4) Overloading (2) Overriding (2) Overviews (1) policies (1) programming (1) Quartz Scheduler (1) Quizzes (17) RabbitMQ (1) references (2) restful web service (3) Searching (1) security (10) Servlets (8) Servlets and JSP (31) Site Usage Guidelines (1) Sorting (1) source code management (1) spring (4) spring boot (3) Spring Examples (1) Spring Features (1) spring jpa (1) Stack (1) Streams & IO (3) Strings (11) SW Developer Tools (2) testing (1) troubleshooting (1) user interface (1) vxml (8) web services (1) Web Technologies (1) Web Technology Books (1) youtube (1)