Hi Peter,
I think for example these two reasons could result better OOP designing,
1-Operator overloading -(coming to
VB.NET in Whidbey).
2-Explicit interface implementation.
especially second one could clarify my meaning you know Explicit interface implementation in C# results better separation from the concept of class and interface ...
Regarding readability,I think both of C# and
VB.NET are the same,if you try to see all codes not just emphasize on some parts,take a look at below code,
Code:
'VB.NET Syntax
If A = 5 Then
DoSomething()
DoSomethingAgain()
End If
//C# Syntax
If (a == 5)
{
DoSomething();
DoSomethingAgain();
}
I think above code in C# is more readable because in C# we separate every statement with ; while in
VB.NET there is nothing(or in C# a==5 while in
VB a=5) but regarding
writability,I think C# is more understandable and better,I mean for a
beginner it's easier to write with C# rather than
VB.NET,for example
Code:
'VB.NET Syntax
Dim x As Y = New Y("ABC")
//C# Syntax
Y x = new Y("ABC");
after all this talk,consider that my migration to C# was from
C++.
_____________________________
Mehdi.
software engineering student.
Looking for a good job for summer 2005.
C# v/s VB.NET
