Fortran

Both Algol and C++

Python

Algol

C++

Ruby and Objective-C

Java and Perl

C++ and Javascript

Algol and Simula

Lisp and Java

It did not support subprograms

Actually, all three of these options represent missing features in the first version of Fortran. They were all fixed in Fortran II.

It could not independently compile separate source code units

It had integers but no floating point data type

Actually, none of these options were missing - Fortran was successful because it supported all of them

PL/1

Short Code

Algol

Plankalkul

Actually, all 4 of these options had compilers or interpreters that were built for them.

Using re-locatable code blocks instead of absolute addressing

Creation of human readable assembly languages

All three of the options listed - relocate-able code blocks, assembly languages, and converting to machine code - were important in the design of high level languages

Expanding pseudocodes into machine code AND the use of relocatable code blocks were BOTH important for the design of high level languages

Expanding pseudocodes directly into machine code before execution, rather than interpreting them directly

Language implementation time

Compile time

Run time

Load time

Language design time

Actually, this isn't true. All variables in a program (in any language) are treated the same way - their max length is the same, regardless of whether they are located inside or outside of functions.

External names have always been limited to 5 letters

External variables are processed using "name mangling", a technique that reduces name sizes.

The full text of external variable names must be placed directly in the compiler's symbol table, and, as result, the number of characters must be limited. 

The binding of a regular java method to its associated object

The binding of storage to a Ruby variable

The binding of a type to a Python variable

Actually, all three of the choices are examples of dynamic binding

Actually, none of the three choices is an example of dynamic binding

Actually this code will not compile since result can not be used inside of the calc function without a variable type declaration

The memory for result will be allocated statically but it may actually be located in one of the other binary images that will be linked together to form the full application.

The memory for result will be allocated statically and will be included in the binary image that the compiler produces for this source file.

The memory for result will be allocated at run-time (on the stack) when the function is actually executed.

The memory for result will be allocated at run-time (on the heap) when the assignment to result is made

Its storage is created when the program starts running and will remain in existence until the program completes

Its storage is created when foo starts executing and will exist only until the foo method finishes executing

Its storage is created when foo starts executing and will remain in existence until Java's garbage collection system de-allocates it.

Its storage is created when foo starts executing but will remain in existence until the program completes

Its storage is created when the program starts running but will exist only until the foo method finishes executing