David,

Good idea. It could even be a SET setting also available through
Tools/Options so that those programmers who like it the way it is
at the moment can keep the present behaviour while others can have
the new behaviour with a DODEFAULT() inserted the moment you edit
a method.

Michel.

================ Original message follows ========================

>Jack,
>
>VFP is more C++ like in terms of this. C++ was used to write VFP. In C++ if you override a method you don't get any of the inherited behavior unless you call it in the overridden code. But in VFP we always get the BaseClass behavior unless you use NODEFAULT. It would be handy if the VFP editor automatically stuck in a :: call or DoDefault() for us like Delphi apparently does. Then all you have to do is move it to the right place of execution. For me at least it's an automatic thing I do whenever editting method code.
>
>>Why does VFP override the methods by default? In a team environment, this can cause many problems. Eventually everyone will execute our macro to "DODEFAULT()" when adding code to methods of our classes without having to think about it.
>>
>>As one adds code to a class in Delphi, it automatically adds a INHERIT keyword. The developer must make a conscious effort to override the parent class code. Doesn't this make more sense? If the purpose of developing classes is for code re-use and inheritance, then VFP should not override by default. This would also be useful when using third party classes...
>>
>>Is this reasonable, or is there a method to this madness?