Comparing C# and VB.NET

re: Comparing C# and VB.NET

Max — Mon, 20 Jun 2005 22:14:30 GMT

Thanks for the explanation. Personally, I prefer the C coding syntax over VB's, but as you pointed out, it's the developer's (or in this case the boss's) choice :)

re: Comparing C# and VB.NET

theCoach — Mon, 20 Jun 2005 22:19:07 GMT

The answer I would be interested in would be is there IL that can be generated by C# code that cannot be generated from VB code (regardless of how much longer the syntax needs to be), and the reverse.

Protections would be one. It is possible as well (but not advisable) to create a class in C# that has both:
private void DoIt() // and
private void doIT()

which is not possible in VB.net, also not CLS.
Things like that. How about Interoping or Unsafe code?

re: Comparing C# and VB.NET

TheoY — Thu, 23 Jun 2005 18:22:30 GMT

Regarding syntax, I'd have to admit that I'm more acclimated to C-family languages (C/C++/C#/Java).

Regarding different IL operations - I'm not an expert at this, but a couple of things come to mind, but most of these require advanced knowledge of the CLR:

(1) VB allows users to make a non-virtual call to a virtual method. I've seldom wanted to do this, except for where I think the API was missing something. For example, when an object overrides Object.GetHashCode(), there usually is no way for other code to access what the original Object.GetHashCode() *would* have returned (which is usually based off of a hash for some uniqueness of each object instance). In VB.NET (and C++ for .NET) you can *non-virtually* call GetHashCode() and actually call into the implementation defined by the System.Object class.

This breaks a lot of assumptions of programmers who are assuming that overriding a base virtual method will obscure the ability to directly invoke the base implementation. I'd take a pretty confident guess too, that most VB.NET programmers either don't use this, or aren't aware when they are using it.

(2) I think "yield" iterators, a C# 2.0 feature, employs a special construct of try/fault under the hood, if you're using "yield" in the scope of a try/finally block.

(3) Like you said, C# supports unsafe code, and VB doesn't. Unsafe code has a whole family of IL operations...

(4) VB allows exception filters (similar to C++/SEH filters) so that you can run an expression while you're deciding to handle the exception. This is useful if you'd like multiple exception blocks to execute the same catch logic, but it makes it harder to discern whether a catch block may or may not be evaluated.

Comparing C# and VB.NET

Comparing C# and VB.NET — Wed, 28 Nov 2007 11:58:21 GMT

PingBack from http://feeds.maxblog.eu/item_757754.html

Website Scripts » D Melodic Minor Accidental : Comparing C# and VB.NET

Website Scripts » D Melodic Minor Accidental : Comparing C# and VB.NET — Mon, 21 Jan 2008 08:11:37 GMT

PingBack from http://websitescripts.247blogging.info/d-melodic-minor-accidental-comparing-c-and-vbnet/