Oh, yeah, lots of those checks were done. For the VFP 9 cycle we used a number of tools to check VFP code and I can't imagine that they've abandoned them.


>>For Al: Mind you, I have been out of the loop for 3 years but the build process *was* automated. The devs would check in code by a certain time every day and the build process would kick off automatically. If we had a build that was a candidate for a milestone, such as an SP or Beta or whatever, we would freeze on that build and test it for some time even though the build system was still spitting out builds every day. In my recollection we rarely had more than one build on a given day - only if there was a critical failure in VFP that prevented us from doing anything or the build process itself failed.
>>
>>I don't know how they are doing it now but if I were to guess I would say that they only do builds when the situation dictates instead of daily since it's not an active product cycle.
>
>Interesting - thanks for the info. I understand VFP is written in C++ - do you know if any LINT-type tools or checks were done against those builds, and if those checks got updated/improved as time went by, so VFP would automatically see the benefits (as long as someone was reading the logs? :))