|
Как стать программистом VB.NET без программистского бэкграунда?
#38372675
Ссылка:
Ссылка на сообщение:
Ссылка с названием темы:
Ссылка на профиль пользователя:
|
|
|
|
_=ДОБРЫНЯ=_Конечно у каждого свое мнение.
Как по мне - vb гараздо удобнее в плане читабельности и понятливости.
Даже тот же - Exit
когда его указываешь - то сразу же видно что конкретно будет делать Exit.
А вообще неплохо было б знать vb и c#.
В том то и дело что нужно не просто указать "Exit" а еще и добавить ненужное слово.
Если код отформатирован правильно, то визуально { } - намного проще воспринимать взглядом чем всякие IF NEXT. Особенно если вложенные циклы.
Пример кода взят с http://msdn.microsoft.com/en-us/library/system.reflection.memberinfo.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1
Сравните визуально одну и ту же часть на VB.NET с C# c вложенными циклами.
Может так получилось что я в жизни встречал много людей, кто программируя на VB.NET перешел на C#, но я не встречал ни одного человека который программируя на C# перешел бы на VB.NET.
В догонку: http://stackoverflow.com/questions/1653895/should-i-learn-vb-net-or-c
Если с английским нормально.
Выдержка из лучшего ответа в спойлере:
I’m an all-out VB enthusiast. So perhaps my answer might carry a little weight, because I actually advise against starting with it.
The optimal solution, as someone has already suggested, would be to learn both languages. This is because both languages have shaped the architecture of the .NET framework considerably. In particular, attempts to preserve compatibility to VB6 have contributed a few odd quirks to the framework.
I also find the C# syntax fundamentally flawed because it inherited the C premise of using largely nonsensical semi-colons, braces and other ASCII trash where keywords would have been more appropriate (e.g. conditional operator, lack of keyword to introduce methods and variable declarations …). You don’t need to agree with this claim/opinion; its purpose here is just to show that I’m not biased in favour of C#, quite the contrary.
That said, C# does have a much larger share of examples on the web, and support tends to be easier to get (just look at StackOverflow). VB also still encourages some bad practices if you don’t pay attention, in particular because Microsoft has irresponsibly decided to make Option Strict Off the default setting, encouraging dangerous loose typing in some places (if you ever touch VB: never use Option Strict Off … except for COM interop scenarios, but in future versions of VB not even there).
Another thing is that they have simply botched lambda support. Both VB and C# offer a very elegant means to express high-level structures in code using queries over data (Linq …). And both use so-called lambdas (anonymous methods, which are declared at the point of usage rather than elsewhere) to express this.
But while the C# syntax for this is concise and very readable, and tries to treat functions like first-class objects, the VB syntax is clunky and impairs readability for no good reason.1) Despite my aversion for ASCII art, keywords are actually the worse choice here.
Consider the two following code samples:
First, C#:
1.
2.
3.
var items = Enumerable.Range(0, 10); // = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
var x = items.Select(x => x * 2); // = 0, 2, 4, 6, 8, 10, 12, 14, 16, 18
var y = items.Where(Number.IsOdd); // = 1, 3, 5, 7, 9
(for a given definition of Number.IsOdd as a static method.)
Now, consider the equivalent VB code:
1.
2.
3.
Dim items = = Enumerable.Range(0, 10)
Dim x = items.Select(Function (x) x * 2)
Dim y = items.Where(AddressOf Number.IsOdd)
FAIL!
I’m sorry to say it, but everything in VB’s design of these features has gone wrong. Since they have become an integral part of .NET programming (even more so in the upcoming version), VB has now a serious disadvantage.
In conclusion, my advise is to start with C# and perhaps try to learn a bit of VB by and by, to get more perspective on .NET. By the way, the same is true for other .NET languages such as F#.
Код на С#
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
// Display information about each assembly loading into this AppDomain.
foreach (Assembly b in AppDomain.CurrentDomain.GetAssemblies())
{
Display(indent, "Assembly: {0}", b);
// Display information about each module of this assembly.
foreach ( Module m in b.GetModules(true) )
{
Display(indent+1, "Module: {0}", m.Name);
}
// Display information about each type exported from this assembly.
indent += 1;
foreach ( Type t in b.GetExportedTypes() )
{
Display(0, "");
Display(indent, "Type: {0}", t);
// For each type, show its members & their custom attributes.
indent += 1;
foreach (MemberInfo mi in t.GetMembers() )
{
Display(indent, "Member: {0}", mi.Name);
DisplayAttributes(indent, mi);
// If the member is a method, display information about its parameters.
if (mi.MemberType==MemberTypes.Method)
{
foreach ( ParameterInfo pi in ((MethodInfo) mi).GetParameters() )
{
Display(indent+1, "Parameter: Type={0}, Name={1}", pi.ParameterType, pi.Name);
}
}
// If the member is a property, display information about the property's accessor methods.
if (mi.MemberType==MemberTypes.Property)
{
foreach ( MethodInfo am in ((PropertyInfo) mi).GetAccessors() )
{
Display(indent+1, "Accessor method: {0}", am);
}
}
}
indent -= 1;
}
indent -= 1;
}
Код на VB
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
VB:
' Display information about each assembly loading into this AppDomain.
For Each a In AppDomain.CurrentDomain.GetAssemblies()
Display(indent, "Assembly: {0}", a)
' Display information about each module of this assembly.
Dim m As [Module]
For Each m In a.GetModules(True)
Display(indent + 1, "Module: {0}", m.Name)
Next
' Display information about each type exported from this assembly.
Dim t As Type
indent += 1
For Each t In a.GetExportedTypes()
Display(0, "")
Display(indent, "Type: {0}", t)
' For each type, show its members & their custom attributes.
Dim mi As MemberInfo
indent += 1
For Each mi In t.GetMembers()
Display(indent, "Member: {0}", mi.Name)
DisplayAttributes(indent, mi)
' If the member is a method, display information about its parameters.
Dim pi As ParameterInfo
If mi.MemberType = MemberTypes.Method Then
For Each pi In CType(mi, MethodInfo).GetParameters()
Display(indent + 1, "Parameter: Type={0}, Name={1}", pi.ParameterType, pi.Name)
Next
End If
' If the member is a property, display information about the property's accessor methods.
If mi.MemberType = MemberTypes.Property Then
Dim am As MethodInfo
For Each am In CType(mi, PropertyInfo).GetAccessors()
Display(indent + 1, "Accessor method: {0}", am)
Next
End If
Next
indent -= 1
Next
indent -= 1
Next
|
|
|
