Information générale
Catégorie:
Programmation Orientée Object
>
>I don't know how much of the above applies to your situation, however, I hope it provides some food for thought.
That's the type of theory explanation for which I was looking. My problem resides mostly with the Visual Classes. We have our standard form for example that contains a SET EXCLUSIVE OFF and SET DELETED ON in the LOAD EVENT. A developer on staff was getting a "File in use" error in a form. Without looking at in detail, I posted a message here thinking that it was a Data Environment problem. After Cetin provided a suggestion to check the SET EXCLUSIVE, a light clicked on over my head. I found that my VFP newbie forgot to "DODEFAULT".
I've never understood why this was not the default behavior in subclasses. My other OOP experience is with Delphi where adding code to methods automatically includes an INHERITED keyword. The developer has to make a conscious effort to override in Delphi. That just seems more intuitive to me.
In a team environment where everyone may not know nor have the time to study the custome code in the parent methods, I would think that a requirement to implicitly state to override would result in less programmer error...
Thanks for the input...
Jack
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement