Re: Translate C# to VB.NET
- From: "Michael C" <mikec@xxxxxxxxxx>
- Date: Mon, 9 Feb 2009 18:30:40 +1100
"Cor Ligthert[MVP]" <Notmyfirstname@xxxxxxxxx> wrote in message
news:OZBWhLfiJHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
Michael,
For Dutch people is speaking (not writing) German or English very easy.
They don't understand why German or people from English speaking countries
don't speak Dutch when they are as guest in our country. Speaking those
languages is so simple, it is almost Dutch.
In my idea are you doing this the same with VB and C#, often contributions
from you in this newsgroup shows this.
On occasion I have forgotten to reply using VB. No big deal.
I write very intensively in C# and when I have done that, I have to
considerate at VB that C# is not VB (and vice vers).
What you said before about VB and C# being almost 1:1 with keyword changes,
I think that is fairly accurate.
Cor
"Michael C" <mike@xxxxxxxxxx> wrote in message
news:uhDsrDdiJHA.3440@xxxxxxxxxxxxxxxxxxxxxxx
"Cor Ligthert[MVP]" <Notmyfirstname@xxxxxxxxx> wrote in message
news:ePUKLwciJHA.996@xxxxxxxxxxxxxxxxxxxxxxx
But it does not take a few days, moreover, it does not take a few days
to learn C#.
Not to learn C# but to *switch* from VB. Perhaps you think C# is more
different from VB than it is.
However, I often get the idea that persons who make programs in C#
thinks that everything is 1:1 the same in VB with the exception that the
keywords are different.
Not 1:1 but pretty close.
Those are often telling here all kind of things which are perfectly
valid for C# but not for VB, because in some cases the languages are a
little in theire syntactical use while that use is not always efficient
as it can be.
There's really not a lot that C# can do that VB can't.
The same exist in natural languages by the way where for some things are
in many languages less words then in the other.
Of course a real language is much harder to learn.
(By instance words as null, nothing and zero in English can give in
programming give much misunderstanding because those have not always an
equivalent in other languages then English)
Naturally there's a few minor differences that you will need to learn.
For example comparing null strings to an empty string will give false in
C# but true in VB I believe. These things aren't that difficult to learn.
Michael
.
- Follow-Ups:
- Re: Translate C# to VB.NET
- From: Michael D. Ober
- Re: Translate C# to VB.NET
- References:
- Translate C# to VB.NET
- From: dwm
- Re: Translate C# to VB.NET
- From: Chris Dunaway
- Re: Translate C# to VB.NET
- From: Cor Ligthert[MVP]
- Re: Translate C# to VB.NET
- From: Michael C
- Re: Translate C# to VB.NET
- From: Cor Ligthert[MVP]
- Re: Translate C# to VB.NET
- From: Michael C
- Re: Translate C# to VB.NET
- From: Cor Ligthert[MVP]
- Translate C# to VB.NET
- Prev by Date: Re: LINQ join(?) question
- Next by Date: Re: LINQ join(?) question
- Previous by thread: Re: Translate C# to VB.NET
- Next by thread: Re: Translate C# to VB.NET
- Index(es):
Relevant Pages
|
Loading