VB = Very Best

[GuyThiebaut]

Nemanja Trifunovic wrote:

You can't extend the syntax of VB with VB and you can extend syntax of some other languages using those languages.

Not sure what you mean by 'Extend' but I have this in all my VB code so that I don't need to use delegates with cross thread calls:

Module Extensions

     \_
    Sub SynchronisedInvoke(synchMe As ISynchronizeInvoke, action As Action)

        If Not synchMe.InvokeRequired Then

            action()

        Else

            synchMe.Invoke(action, New Object() {})

        End If

    End Sub

End Module

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[Nemanja Trifunovic]

GuyThiebaut wrote:

Not sure what you mean by 'Extend'

I mean like with Lisp macros. For instance, Scheme doesn't offer any out-of-the box support for object oriented programming, but because it has Lisp-type macros, people wrote extensions (such as ScmObj[^]) that turn Scheme into an OOP language. A nice explanation of Lisp macros can be found here: http://lists.warhead.org.uk/pipermail/iwe/2005-July/000130.html[^]

utf8-cpp

[Ennis Ray Lynch Jr]

Do you want a pointer on what vb can't do. Some times it is hard to point out specifics. Maybe some of the C++ guys will chime in with a few pointers.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch

[GuyThiebaut]

I see what you mean :thumbsup: I was looking at Haskell recently(can't claim I understood it).

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[David Crow]

tmik wrote:

Is there any one who can pin point the things VB can't do while other languages can do.

Is that the differentiating factor you use to guage whether one language is better than another? If so, then no answer will suffice.

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous

[Ranjan D]

It's not possible to write in VB.NET and peoples simply don't except the truth :laugh: Unsafe code - http://msdn.microsoft.com/en-us/library/aa664769(v=vs.71).aspx[^]

Ranjan.D

[Silvabolt]

VB: Dim num As Integer C#: int num; For every integer I declare, I have to press ~10 more keys in VB than C#. It gets worst as my code becomes longer and you end up seeing a ton of Dims and unnecessary text. It takes longer to read through, iffy looking syntax... What exactly is a 'Dim' anyways? If you research the answer to this, you will realize that it's definition is not intuitive anymore and wrongly used based on what it's supposed to mean.

[Dave Kreskowiak]

That's easy, C/C++/C# style "pointers". That alone makes image processing SOOOO much easier.

A guide to posting questions on CodeProject[^]
Dave Kreskowiak

[Mycroft Holmes]

Marc Clifton wrote:

VB programmers were cheaper and more readily available

I have found there are more skilled resources in c#, and the fact that 80% of all articles and examples seem to be in c# was enough for me to take the team from vb to c#.

Never underestimate the power of human stupidity RAH

[Vark111]

Here's one I run into almost everyday: When I override Equals(), I must also override GetHashCode(). Most Hashcode calcs require math that will quickly overflow an integer. No worries, I can simply turn off overflow checking and let it overflow - the function still performs properly. Here's the rub: in C# I can leave the assembly as checked, and just mark my GetHashcode() method as unchecked. Can't do that in VB. You can only mark the entire assembly as checked or unchecked. At least, that's the way it was in 2008. Stopped using VB at that point.

[PIEBALDconsult]

Marc Clifton wrote:

VB programmers were cheaper and more readily available

And larger about the chestal region. :cool:

[PIEBALDconsult]

Several; the limitation that comes to mind first is that in VB.net you can't define an event based on a delegate that returns a value. The only places I see VB.net as better than C# is in how to declare an Extension Method and VB.net's support of method-scoped static variables. VB.net has a lot of historical baggage that weight it down. C# is better than VB.net because C is better than BASIC.

[StatementTerminator]

VB can do anything other languages can do, only worse. Actually, the real problem isn't the language. It's the people who tend to use it because it's "easy." Using spray paint is easy too, as long as you don't use it well.

[Lost User]

Curly braces