Hi Einar,


>>Not sure what point you're trying to make here. From a theorectical point of view you're right. However from a pratical point of view it is different. For the average database application you won't see any significant difference in speed. Whether it is strong or weak typing. VFP is well known for it blazingly fast database handling and outperforms .NET datahandling on most aspects. VFPs rich language that makes it possible to do complex calculations/algoritms within on command makes issues with strong vs weak typing irrelevant.

>Yeah I guess my point was kinda theoretical, but keep in mind there is a loop in every app and you always want to make the loops fast <s>

I don't, I just don't want the loop to be a problem.

>Well I guess you caught me in a lie :) The main reason that VFP's compiler is so fast is because it doesn't check for hardly anything :) If you get a compile error in VFP there is something really screwed up :)

Actually that is not true either. The real reason for VFP beeing so fast is that nothing is compiled to native code and a lot of resources like forms and classes are already compiled while saving it (unless doing a recompile). The VFP compiler merely has to add the SCX,SCT and VCX,VCT files to the VFP exe header and it works. It is just the definition of how a VFP exe is build up that makes it fast.

>>>2. I love the fact that C# catches most of my silly mistakes at compile time. It takes a lot of resources fixing a bug that got into the run time compared to catching it in the compiler.
>>
>>Personally I think compile time is way too late. It should give you hints when writing the source code.
>
>C# already does this. It will put in colored squiggly lines while you are typing to notify you that something isn't right. Or if intellisense doesn't work there is a good chance that you have not propperty declared an object. Even if this is a nice feature I am usually to quick with my keyboard shortcuts to build after I have added code to notice the squigglies.

OK...

>I also came from a C (and Pascal and several scientific languages like MatLab and IDL) background before coding VFP, so I guess I went full circle (strong to weak and then back to strong). I was (and still am) a big supporter of VFP, but I don't regret switching to C#.

Everyone has to make that choice themselves..

Walter,