It might make .NET "better" ... but better for what ? VB was better for "general programming". C/C++ was better for "systems programming". Lisp is better for AI.

With all its bells and whistles, .NET is still not "better" at hard-core "database programming" than VFP ... if that's what you're looking for.

What from the list below do you think you "need" right now (other than the usual "strong typing") ?

Give real-world application requirement examples to back up your choices :)

>Hello world,
>
>In the August issue of FoxPro Advisor, Kevin McNeish spells out in his article "Visual FoxPro and .NET" all the reasons he thinks .NET is better than FoxPro.
>
>Object Oriented features
>- abstract classes & methods
>- interface inheritance
>- overloaded methods, structures, enumerations
>- custom events
>- static class members & attributes
>- templates
>- anonymous methods
>- iterators
>- partial types
>- requirement to explicitly override parent method
>
>Other feature
>- option to enforce strong typing
>
>Perhaps every item on his list, or almost every item, could be an enhancement and incorporated into the next FoxPro version.
>
>I would write to Ken Levy myself, but I could not find his e-mail address after two minutes of looking. Anyway, a request would carry a lot more weight if the UT community were behind it.
>
>People who know more about the features that Kevin McNeish mentions may be able to make improvements and/or corrections to my list, and I would welcome that.
>
>What do you think?
>
>Thanks,
>
>Rick Graves