What is type safty in dot net?

  • Thread starter Thread starter Bhuwan Bhaskar
  • Start date Start date
Bhuwan Bhaskar said:
What is type safety in Dot net?
Click to expand...

Well, that's a very broad question. What's the context? What exactly
are you trying to find out?
 
Essentially, it means that the compiler won't let you treat an apple like a
trampoline.

In other words, the compiler looks at the "type" you are working with in
your statements and makes sure that you only do things with or to that type
that are allowed for that type.

C# has this automatic type-safety built in by defalut. With VB .NET, you
must change the Option Strict setting in Tools...Options to On (the default
is off).

-Scott
 
Scott said:
Essentially, it means that the compiler won't let you treat an apple like a
trampoline.

In other words, the compiler looks at the "type" you are working with in
your statements and makes sure that you only do things with or to that type
that are allowed for that type.

C# has this automatic type-safety built in by defalut. With VB .NET, you
must change the Option Strict setting in Tools...Options to On (the default
is off).
Click to expand...

VB.NET is actually type safe regardless of the Option Strict setting.

With the setting off it allows a lot of implicit conversions that is not
allowed in strict mode, but the conversions are still type safe. If the
conversion would produce an unusable result, you get a runtime error
instead.
 
Well, I think when most folk talk about type-safety, they are referring to
design-time, not run time. After all, with your definition, you could make
the argument that VB .NET is also bug-safe, since you'll get a runtime
exception or runtime anomoly when the program encounters bugs. If there
were such a thing as a bug-safe language, you'd expect it would indicate a
bug as your were creating the bug.
 
Scott said:
Well, I think when most folk talk about type-safety, they are referring to
design-time, not run time.
Click to expand...

Then they are confused, as that is strong typing, not type safety.
After all, with your definition,
Click to expand...

The definition is not mine.
you could make
the argument that VB .NET is also bug-safe, since you'll get a runtime
exception or runtime anomoly when the program encounters bugs.
Click to expand...

Not at all. A bug can very well result in a perfectly normal result,
even if it isn't the correct result.
 
Hi Göran,

what are your views for 'type safety' and 'strongly typed' in dot net. I
will be obliged if you make my concept clear on these terms.

Thanks,

Bhuwan
 
Bhuwan said:
what are your views for 'type safety' and 'strongly typed' in dot net. I
will be obliged if you make my concept clear on these terms.
Click to expand...

A type safe language won't allow operations or conversions that can give
an illegal result.

For example, converting a Long to an Integer i VB.NET will check that
the value is actually possible to store in an Integer.

A strongly typed language enforces type conversions to be explicit.

For example, with Option Explicit On VB.NET will not implicitly convert
a string to a number, but with Option Explicit Off, it will.


Type safety:
http://en.wikipedia.org/wiki/Type_system#Safely_and_unsafely_typed_systems

Type strength:
http://en.wikipedia.org/wiki/Type_system#Strong_and_weak_typing
 
Back
Top