David: Of your four options I choose #1. ;-)
Jody Bevan ARGUS Productions Inc. Developer Argus Productions Inc. <https://www.facebook.com/ArgusProductions/> > On Aug 2, 2017, at 11:34 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > > Without compile-time verification of source code errors, you're left with > these options: > > * Write perfect code every time. > > * Write you own code scanner. Parse your code and process whatever tests > and checks you can use. This is very fruitful, but a ton of work. It's hard > to see anyone but a highly motivated individual or a large team doing it. > > * Write very thorough test cases to generate realistic runtime conditions > to test your code. 4D doesn't have any real test harness available and it's > not the simplest environment to test anyway. I've seen some good efforts > and devoted quite a bit of time to this sort of thing myself. Again, price > of entry is higher than nearly any 4D shop can pay. (Yes, there is a > UnitTester component from V12 that can be converted...but it only aims to > solve some problems and you'll still need to retrofit zillions of white box > tests.) > > * Run you code and deal with the errors when they crop up. At your > customers. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
