[trevster344]

BobRodes, on 13 November 2012 - 01:08 PM, said:

Trevster, the idea that VB6 is not an object-oriented language and VB.Net is is not entirely accurate. VB6 has (nearly) all of the characteristics of OO except white box reuse. Most people who say that VB6 is "not an OO language" say so because of this missing characteristic. However, VB6 is definitely "oriented" to the use of "objects."

Oh I know it's an Object Oriented Language all in its own. I didn't mean it that way Bob. What I meant is the presence of the fundamentals is definitely not as blatant as in VB.Net.

[BobRodes]

trevster344, on 19 November 2012 - 11:07 AM, said:

BobRodes, on 13 November 2012 - 01:08 PM, said:

Trevster, the idea that VB6 is not an object-oriented language and VB.Net is is not entirely accurate. VB6 has (nearly) all of the characteristics of OO except white box reuse. Most people who say that VB6 is "not an OO language" say so because of this missing characteristic. However, VB6 is definitely "oriented" to the use of "objects."

Oh I know it's an Object Oriented Language all in its own. I didn't mean it that way Bob. What I meant is the presence of the fundamentals is definitely not as blatant as in VB.Net. />

Well, yes.

[BobRodes]

raziel_, on 19 November 2012 - 03:09 AM, said:

@BobRodes everyone can look at VB6 as it wants. You can look at it as Object Oriented which in a way is given that you can initialize classes forms etc. It dose not have inheritance and/or polymorphism but if you want to look at it as a Object Oriented is fine by anyone as much as you want. />/>/>/>

Actually, that's not entirely accurate--polymorphism is alive and well in VB6. Have a look at this:

'a Public class called iAnimal
Public Sub Move()

End Sub

Public Sub Bite()

End Sub

'Now, a class called Flea, set to PublicNotCreateable
Implements iAnimal

Private Sub iAnimal_Move
msgbox "boing boing"
End sub

Private Sub iAnimal_Bite
msgbox "nip"
End Sub

'And a class called TRex, also PublicNotCreateable
Implements iAnimal

Private Sub iAnimal_Move
msgbox "KABOOOMMMM....KABOOOMMMM...."
End sub

Private Sub iAnimal_Bite
msgbox "CRRRUUNNNNCCCHHHH"
End Sub

'Now, a client

Public Sub cmdAnimal_Click()
dim x as iAnimal
dim y as iAnimal
set x = new Flea
set y = new TRex
x.move
x.bite
y.move
y.bite
End Sub

As you can see if you try out this code, polymorphism and black box reuse ("interface inheritance", in Microsoft marketspeak) are clearly supported by VB6.

This post has been edited by BobRodes: 20 November 2012 - 08:04 AM

[martinp]

My understanding is that VB6 is very close to VBScript? Although I'd rather not code in either, unfortunately, I'm an automated tester. And, the tools of testers are pathetically behind the times. QTP, the industry leader >USD10,000 per install, still uses VBScript. Not legacy code, but a legacy application. />

[BobRodes]

VBScript is a subset of VB6. For example, all variables are of Variant type, and you can't build COM components with it.

[Rishif2]

according to me vb6 is very useful for new programmer (Beginners).
although microsoft has released VS 2012 but vb6 is still in fashion due to its flexiblity.
i know that after getting into vb.net , C# you will say that vb6 is not in treand but it is oops based and really roboust language.
so as conclusion i can say that you can opt vb.net , c# and if you are advanced OOPS programmer than J# also. but cannot say that learning vb6 is waste of time.

[Curtis Rutland]

Quote

vb6 is still in fashion due to its flexiblity

VB6 is in fashion because it's deeply embedded into a ridiculous amount of businesses, not because it's flexible. VB.NET is way more flexible in its uses than VB6, considering WPF, WCF, ASP.NET, ASP.NET MVC, WinForms, Windows Services, Console, Windows Phone 7, Windows Phone 8, Windows Store Style, Windows Workflow, etc...can all be made with .NET

Quote

if you are advanced OOPS programmer than J# also

That's just nonsense. J# hasn't been supported or updated for a long time. It was completely abandoned.

[cfoley]

Quote

you will say that vb6 is not in treand but it is oops based

oops  
/o͝ops/
Exclamation
Used to show recognition of a mistake or minor accident, often as part of an apology.

Yes, yes it is.

[Cooldude68]

Anybody that says VB6 is out of date has his/her reasons but for me, it‘s the best i mean the best place to start for a learner.
It‘s easier to code and it also does wonderful things.
I have some close to me that has developed a bucketload of applications using VB6.
Student result-processing system, chat application, payroll softwares e.t.c

[Curtis Rutland]

Quote

it‘s the best i mean the best place to start for a learner

And I keep telling you people that it's a terrible idea to start with. There's literally no reason to start teaching students VB6 when there are other languages that are just as simple, just as flexible, and not 15 years out of date. VB6 hasn't been updated and won't ever be updated again. Why not start learning a language that's actually current? For example, you can do anything with Python that you can with VB6, it's just as easy to learn (easier maybe) and is currently supported and developed. Or VB.NET. Or Ruby. Or anything not VB6.

Classic VB programming has its place. Legacy work. That's it. Every new application written in VB6 is one that should have been written in something else.

[cstrouse]

Curtis Rutland, on 08 November 2012 - 07:16 AM, said:

I see VB6 as the new COBOL. Something that nobody (in the west) teaches, but will be a required skill for lots of jobs for many years to come. All because of deeply embedded legacy systems.

Learning it now would be useful if you want a job doing that: maintaining or porting legacy systems. I would think people would learn it out of necessity when they're tasked with that, not seek it out. If you want to make new applications professionally, VB6 is unlikely to be something that gives your resume a boost, considering just how far out of date it actually is.

Quote

the ease of creating and using COM objects, and the ease of creating wrappers for the Win32 API

I wouldn't know about COM, but I do know that P/Invoke is just the bee's knees for Win32 interop. It's pretty simple for VB.NET/C# to wrap Win32, so that's not really an advantage for classic VB.

I've seen quite a few mission critical business apps written in VB6 at organizations that don't have the resources in terms of money, time, or available staff to port the application over to .NET and fix whatever bugs pop up and replace custom controls and such. I also know some hardcore VB6 developers who love it because it feels faster to than .NET without all of the .NET framework overhead.