Sundial Service
Delphi Developer |
Wed, 18 Jun 1902 08:00:00 GMT
Re:Clipper App Upgrade - VB or Delphi..?
QuoteGordon Hamm wrote: > Of course, you are going to get biased answer here, but Here's my 2cents.. > worth.. > I programmed in Clipper for about 8 years. Delphi made the most sense for > me.. > VB was just to lame. I always seemed to hit a wall. Visual Dbase was just > too bulky, I.E. runtimes etc. Also, very very poor low level abilities. I > would say the same for Visual FoxPro.. > In Delphi, I can write a simple app by dragging and dropping, or a real > intense multi threaded one.. I dont feel limitations. > Also, I use Halcyon that lets my do all my good old Clipper stuff in > Delphi.. > I end up with just one exe, no runtimes , DLL's etc. You use the same xbase > syntax.. check out http://www.grifsolu.com > I think the saying "Delphi is V.B. on steroids" is accurate..
My 2C on the question would be that "both languages are more-or-less equally expressive for this purpose, and the distinction may not be relevant at all." :-) !! When you are looking at converting a clipper app to <anything else>, the distinctions between a compiler and an interpreter, between InPrise and Microsoft, really do not have any relevance(!!) at all. What matters, and all that matters, is how closely the environment-of-choice maps to the Clipper environment, if indeed it does at all. (And it probably doesn't.) Clipper is, of course, an interpreted or psudo-interpreted environment, optimized (in the manner of all programs-of-its-era) for the purpose it is designed to achieve. Neither VB nor Delphi are particularly optimized in this way. It may be that some other "4GL" might actually be more suitable. The original poster of this thread may well be advised to stop and think, "why did I select VB and Delphi as my candiates, and is this choice actually defensible?" Also, "why did I limit my choices to VB and Delphi?"
|