>>Since there are some people on this thread who have used both Delphi and VFP, I'd be curious to know the following. I have heard a number of claims the Delphi is also far superior to VFP in terms of bug handling. True or False?
>>
>>1) A claim was made that Delphi programmers spend a lot less time working around Delphi bugs than VFP programmers do getting around VFP bugs.
>
>Bugs in VFP? Maybe it depends a lot on what kind of systems you develop with VFP. I have'nt seen a VFP bug in a while. I use VFP 6 with SP3 and everything goes pretty well. There are some things I have'nt touched in VFP (ADO for example) so maybe there could be bugs there but it doesn look like it. If you are ever faced with a weird bug in VFP there is a superb reference that will help you get rid of those bugs. There is a book called "Hacker's guide to VFP 6.0" and it covers everything related to VFP 6.0
>
It may be heretical, but there are a number of bugs in VFP6 SP3, and MS publishes new KBase articles and workarounds for them frequently. The bugs are often fairly subtle or hard to exactly duplicate, especially given the interpretive environment, but they do exist. Some are not terribly subtle. Most have workarounds.
The native VFP language is much richer than the native Object Pascal language - you'd end up having to write or buy a good deal of code to duplicate the native language functionality. C/C++ as a base language is probably cleaner than either VFP or Delphi, but Markus Egger's tagline summarizes it well:
Visual FoxPro: Because life is too short to code in C++...>>4) The claim was made that the borland debugger works much better than the VFP debugger -- and that finding and fixing programmer errors was also faster than in VFP.
>
>I never used the Delphi debugger but I can tell you that the VFP debugger (since VFP 5) is really something. I can't say if it is the case but I heard that the VFP debugger is the same as Visual C++.
>
It's similar to but not the same as VC++'s debugger - it operates at an entirely different level. The complaint sounds like someone who hasn't worked much with the VFP debugger recently. The VFP 6 debugger has improved a great deal, and the availbility of the interactive, interpreted environment within the debugger (ie you can get to the
Command Window and do things at a breakpoint) offers large advantages.
Since there's probably more programmer-written code, and are probably more third-party products involved in a large-scale Delphi project, there are more wrong turns available. OTOH, you may not have 15 different ways to do something that are syntactically correct, a frequent problem with people from different development perspectives working with a common code base.
