>If I was serious about continuing to learn OOP but avoid pointers and >references, wouldn't Java be a good choice? If you think how many times one >actually subclasses non-visual classes, then VB certainly provides a logical >path for one sticking with the MS camp. But what is your opinion on this?
For line of business apps, I don't see Java as a great tool. Would you use C++ to build a database app for the marketing department. For building components that are part of a bigger solution, then Java could be a good fit.

The learning curve for many I suspect would be steep. I include myself in this camp as learning Java or C++ would be a radical departure from the primary langauges I use now: VFP and VB.

From an OO standpoint, I see your point, but to me, that is more of a theorhetical/academic issue. Yes, you can build OO apps with Java. But, that aside, could you build efficiently with Java, particularly a line of business app? I don't know - and in the absence of not knowing - I am likely to reserve judgment on advising others to migrate to Java. OO is nice -but you have to be able to build apps in the first place in order to take advantage of OO that a particular environment offers.

>Supercede is a good suggestion for the Java route as it compiles to true machine code and supports ActiveX and JavaBeans on the Wintel platform. It also allows C++ coding, too. I've attempted to install VJ++ tech preview on two machines without success, so I can't comment on it.

I don't know squat about supercede and therefore cannot comment.


>BTW, what is the 20% that you can not achieve in VB as compared to VFP?

I think my words were to the effect that of the stuff I do in VFP, 80% is easily portable, 20% would be a bit difficult. Areas like string manipulation and places where I would use native data access constructs. These areas would have to be re-worked. Nothing impossible here - just takes a bit of extra work.