At 11:15 2015-07-13, Ken Dibble <[email protected]> wrote:
I would just add that it is not necessary to compile a VFP program
to test it. Just run it. If you do that first, you will find out if
your code is working immediately. When you know that, then you can
safely attribute failures in the compiled version to the compilation
process and not to your code.
Plus, it saves time....
Unless you get bit by set development off or some caching or
_____. (If there is not always something else, that is still a close
approximation.)
I almost always compile before testing. When I do not, I do
not count it as sufficient to release the code.
I prefer to reset my environment when I start testing. That
includes a fresh compile.
Many years ago, I had a program that was not working
right. Over a period of about two hours, I finally narrowed the
error down to one page of code. When I examined that code, I saw
that there was no way that it could causing the error. I refreshed
my environment, and the "bug" was gone. I still do not know what
happened, but suspect that a previous try of the code corrupted
something that I was counting on.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
