> >Dorris, I can't wait until the MS Fox development team decides to > implement strong typing. Weak typing while convenient is inherently low > level (see pointer). Perhaps I will put this on the "wish list". :-) > > > >Perhaps a fox editor that uses colour coding for variables would be great. > Green for numberic, red for character or perhaps a right click on a > variable would indicate the scope, type and place of declaration. > > Really, trust me......I can wait! I am already having way too much fun > trying to figure out how to do some of the stuff my users' want without > having to worry about typing variables! Now people will start talking about me for always taking ladies' side, but... strong typing is, IMO, a way to leave some work to the programmer, where the machine should have done it. The reason for introducing strong typing was not to discipline programmers and make them write cleaner code (what do you mean with "clean" if a variable is defined six screens before it's first used?), it was that thus the variables could be compiled to fixed locations, and that the compilers could be made single-pass. In those days the compiling speed was substantial issue. If fox had gone strong-type, imagine how many functions would have to be redefined - imagine things like Between(), Padl() and such, which work ok no matter the type of data you stuff 'em with. And our functions, written for undefined types. In VFP, strong types may be only optional, for those who like it.