Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
A better debugger
Message
From
09/02/2000 16:12:07
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00327132
Message ID:
00329704
Views:
22
Hi Joe. No apology needed.

>
>*//* The IDE (Developer Environment) differences that I find unattractive:
> 1. Search ability. FoxPro limits your scope SO much. VB allows great flexibility. i.e. selected text, current procedure, current module, whole project that last one is the real bite for me in FP as I am maintaining a lot of code I did not write which is sometimes organized by Satan to torment me.

I agree here. Some better search tools would be nice.

> 2. The actual layout of the source I would like to have the option to see everything at once or one method at a time (VB) as opposed to being restricted to single method view. (Maybe this is a by product of whatever causes the search limits.

I think FP does it the right way. It helps you think about encapsulation better.

> 3. Some of the VB bells and whistles from VB would be well received FP I feel. The capitalization of prototyped variables is persistent in VB. The auto-complete is very nice.

Intelisense in FP was demonstrated at DevCon as a feature in VFP 7.0. I'm not sure what you mean by auto-complete.

> 7. The one thing that really chaps my behind the worst in FP is when you are debugging and you stop or cancel the forms are often left in use. And you go round after round every time you stop debugging. :/ In VB you click the stop button or ctrl-break then stop button and viola your ready to get back to work.

I agree here too.

> 8. Inheritance, encapsulation, polymorphism, and subclassing in VB would be MORE than real nice.

VB has encapsulation and polymorphism.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform