Visual Studio Next Generation: Language Enhancements

Type Safety

Today the Visual Basic language is very liberal in the implicit type coercions that it will generate. For assignment and for parameter passing other than by reference, the Visual Basic compiler will allow nearly any data type to be converted to any other type by generating runtime coercion. The runtime coercion operation will fail if the value that is to be converted cannot be converted without data loss. Through the addition of a new compilation option, Visual Basic can generate compile-time errors for any conversions that may cause an error at runtime. Option Strict improves type safety by generating errors when a conversion is required which could fail at runtime or which, like the automatic conversion between numeric types and strings, is unexpected by the user.

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“In theory, theory and practice are the same. In practice, they're not.”