Visual APL supports both early and late bound objects.

With the support of dynamic and strong types, Visual APL also supports early and late bound objects. Dynamic typing has always been a hallmark of APL, bringing the strength of transparent array manipulation and type promotion to complex applications.

However, with dynamic typing there is always a small subset of an application which must rely on external strong typed code, often created in C, C++ or assembler to address specific performance issues.

With Visual APL you can use strong typing right in your APL functions.

One of the benefits of strong typing is that methods on a type can be defined at the time the application is created, thus avoiding the cost of looking up the method each time it is referenced. A simple example is the delete trailing blank function we have all used; in Visual APL you can just type a variable like this:

string stxt

That's it, you just agree that stxt will always be a string, and you get early binding, meaning your code will be as fast as possible.

You delete the trailing blanks like this:

stxt.TrimEnd()

To delete leading blanks:

stxt.TrimStart()

To delete leading and trailing blanks:

stxt.Trim()

It's just that easy. You don't even have to know what methods to call on the string type, the intellisense will help you. Write your function, dlb for instance, type the variable, and you have early bound code, and no one can write a faster version.