Which term describes a class that has data types that are NOT checked at compile time?

Which term describes a class that has data types that are NOT checked at compile time?

Which term describes a class that has data types that are NOT checked at compile time?

A.
late-bound

B.
static

C.
early-bound

D.
strongly typed



Leave a Reply 7

Your email address will not be published. Required fields are marked *


Jimbo

Jimbo

Perhaps I am misreading the question, but I was expecting this to be late-bound. Just because things are static doesn’t mean they are ignored at compile time??

Cecil

Cecil

late-bound? I think early-bound should be right.

Andriy

Andriy

It can’t be early-bound bacause this means that you use a strongly typed proxy class. This is why the types can be checked at the compile time.

For some reason, in my practice test the right answer is B (static) which doesn’t make sense.

Abhi

Abhi

Should be ‘early-bound’!

Frank

Frank

Answer is A since Early-Bound means that the data types are checked at compile time!

Frank

Frank

From MSDN : The advantages to using early-bound entity classes is that all type references are checked at compile time.

Carlos

Carlos

The MSDN says:

The key difference between early and late binding involves type conversion. While early binding provides compile-time checking of all types so that no implicit casts occur, late binding checks types only when the object is created or an action is performed on the type. The Entity class requires types to be explicitly specified to prevent implicit casts.

therefore the right answer is A. late-bound

https://msdn.microsoft.com/en-us/library/gg309272.aspx