Marshalling Types
Until this chapter, we wrote Core Perl programs without worrying about typing, as Perl has a dynamic typing system. .NET is a strong-typed environment: There is one-to-one correspondence between variables and types. In other words, every variable has one and only one type associated with it.
We do not have to change our attitude with respect to types if our PerlNET program contains Core Perl statements only. However, the problem may occur when working with .NET components and classes.[2] As we saw in our first sample program, working with .NET classes involves calling methods.[3] Many of the methods expect arguments, and we have to supply arguments of the correct type. Consider the following code example from the Marshalling\Types ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access