Adds Cross Compilation and Basics of Interpreters in the Week 2 section #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
meshtag
suggested changes
Dec 18, 2021
| - An interpreter generally uses one of the following strategies for program execution: | ||
|
|
||
| - Parse the source code and perform its behavior directly. Ex:- dBASE and BASIC | ||
| - Translate source code into some efficient intermediate representation or object code (ex bytecode) and immediately execute that. Ex:- Java |
There was a problem hiding this comment.
In previous property, will there be no IR formation/transformation? My opinion is that regardless of the strategy of interpreter, IR formation/lowering will happen always. If efficiency is the major point of difference between both strategies, can you explicitly highlight that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.