Ed,
Is VFP meant to be a high level (english like) language, or not? As languages progress surely we need to be shielded from the intricacies under the bonnet (make that hood), so that we can get on with addressing the complex and ever changing issues that our clients employ us for? Speaking from personal experience I see more than enough poor quality code - that I am glad many of my colleauges do not attempt to use Win32 in their developments. It would be useful however if VFP had high level contructs for thread creation and management.

And I do not know how we survive without Call Backs. In another thread a developer is talking about implementing FTP by moving n bytes of his file at a time - just so that he can display a progress bar! I think we lose out because of an inability to do most things in VFP asynchronously.
Regards,
Houston.


>>>They have to be to escape the brain-damaging crutches imposed by the language. A simple test - what percentage of VFP developers know what in the context of a process or a thread, the concept of a handle represents, as opposed to a token or an id? I'd venture to guess that the percentage is vanishingly small, especially when compared to people developing in C++ or Java. The typical VFP programmer isn't aware of what the differences are, and won't lift a finger to learn it unless jabbed repeatedly with a powerful cattleprod. The lack of initiative on the part of the VFP developer community creates the need for 'backwards compatibility'. How much hue and cry came from the BASIC developers when BASIC transiteds to VB, and gave up a whole lot of 'backwards compatibility' in the process.
>>
>>Ed,
>>
>>Interesting.
>>
>>However, does that knowledge impute any sort of superiority in terms of being necessary for daily productivity? For example, by removing the need to know all that stuff you enable the "tool user" (ie. developer) to be more productive. How much productivity would be gained by this do you think?
>>
>
>I think that the VFP community has suffered as a whole from being 'shielded' from basic Windows principles and practices; by not understanding the basis of things like the event loop, Windows handles, and the panoply of standard Windows facilities and interfaces, the average VFP developer is at a loss when forced to play in the general WinApp environment. Even the concepts of things like threading are garbled by the use in VFP's documentation. And the result is that a lot of programmers fail to leverage what's there for our use.
>
>>I think at some point a good developer reaches the point where they recognize that in addition to learning their tool of choice that they themselves are their own primary tool. As such they then become interested in books like "Code Complete" for example.
>>
>>But for the most experienced developers to gain their sense of self-worth by pointing out that others are not as superior as they are is IMO a huge dis-service to the community, no matter how satisfying it may be to point at others and laugh.
>>
>
>I don't laugh; at this point, I simply stop trying to offer my POV sooner.
>
>>Each developer should take responsibility to enlarge their own abilities continually. Some are better and faster than others. Thos who are 'better' IMO have a greater responsibility to those who are not; to help them along.
>>
>>I am curious and perhaps you or John would know the answer.. Does the typical VB, C++ or other community have the same sense of community that the Fox community does? And, is it better or worse?
>>
>
>No, we have a strong developer community, but it lacks strong understanding of the sandbox we play in.
>
>>Personally, I do NOT think VFP programmers are superior -or- inferior than other developers. I also do not think that proficiency levels of any sort impute any kind of superiority other than technical. I have seen many technically 'superior' developers make a tremendous mistake and attempt to garner for themselves a certain kind of moral superiority and that's sad IMO.
>>
>>Surely there's more to life than one's technical expertise... <g>
>>
>You mean the ability to perform walletectomies? ;-)