> Well, I think when most folk talk about type-safety, they are referring to
> design-time, not run time.
Then they are confused, as that is strong typing, not type safety.
> After all, with your definition,
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.
Not at all. A bug can very well result in a perfectly normal result,
even if it isn't the correct result.

Signature
Göran Andersson
_____
http://www.guffa.com
Bhuwan Bhaskar - 22 Oct 2007 05:32 GMT
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
>> Well, I think when most folk talk about type-safety, they are referring
>> to design-time, not run time.
[quoted text clipped - 11 lines]
> Not at all. A bug can very well result in a perfectly normal result, even
> if it isn't the correct result.
Göran Andersson - 22 Oct 2007 07:22 GMT
> 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.
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

Signature
Göran Andersson
_____
http://www.guffa.com