Information Technology Reference
In-Depth Information
GetAt(row, column), and other APIs. The implementation you have in
your head would not use dynamic objects in the API, or even in the imple-
mentation. You can meet those requirements with static typing. You
should. You'd only use dynamic in the public interface when it is needed.
Dynamic types are a useful feature, even in a statically typed language like
C#. However, C# is still a statically typed language. The majority of C#
programs should make the most out of the type system provided by the
language. Dynamic programming is still useful, but it's most useful in C#
when you keep it confined to those locations where it's needed and con-
vert dynamic objects into a different static type immediately. When your
code relies on a dynamic type created in another environment, wrap those
dynamic objects and provide a public interface using different static types.
