ADVANCED TOPICS IN COMPILER DESIGN
CODE GENERATION FOR OBJECT ORIENTED LANGUAGES
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
A classic method for learning programming with commands to control movement and drawing of an on-screen robot called a “turtle". The turtle hearkens back to early implementations in which children programmed a physical robot whose dome-like shape was reminiscent of a turtle.
|
|
A problem solving approach (also known as stepwise design) in which you break down a system to gain insight into the sub-systems that make it up.
|
|
A method of programming in which two programmers write code using a single computer. One programmer in the “driver” role uses the mouse and keyboard to actually write the code while a second acts as a “navigator", keeping track of the big picture, catching errors, and making suggestions. Programmers switch roles frequently and communicate throughout the process.
|
|
·:A programming language that captures only the most primitive operations available to a machine. Anything that a computer can do can be represented with combinations of low level commands.
|
Detailed explanation-1: -A top-down approach (also known as stepwise design and stepwise refinement and in some cases used as a synonym of decomposition) is essentially the breaking down of a system to gain insight into its compositional sub-systems in a reverse engineering fashion.
Detailed explanation-2: -OVERVIEW. Top down analysis is a problem solving mechanism whereby a given problem is successively broken down into smaller and smaller sub-problems or operations until a set of easily solvable (by computer) sub-problems is arrived at.
Detailed explanation-3: -The top-down approach in software development is a method of designing and building a system by starting with a high-level design and then progressively refining the design with increasing levels of detail. It is also known as the stepwise refinement approach.
Detailed explanation-4: -Stepwise refinement is sometimes called top-down design, for the obvious reason that you start the process at the top, with the problem as a whole, and work downwards. Top-down design involves looking at the whole task and breaking it down into smaller, more manageable sub-problems which are easier to solve.