Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SCATTER NAME
Message
De
12/01/2001 14:06:18
Larry Rix
Larry Rix & Associates, Inc.
Westminster, Colorado, États-Unis
 
 
À
12/01/2001 13:56:49
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Titre:
Divers
Thread ID:
00463096
Message ID:
00463134
Vues:
17
True enough Mike, and I agree. Hopefully, the programmer would be on-the-ball enough to pay attention to naming conventions. Actually, the wrapper class approach bears tremendous merit. Consider:

SCATTER NAME THIS.ioMyEntity

where the current table has some the structure:

emp_name
emp_ssan
emp_id

The wrapper class cstEmployee might then have the following:

cstEmployee.qcEmployeeName( )
cstEmployee.qcSSAN( )
cstEmployee.qiEmployeeID( )

The query methods then have the knowledge of how to access the data brought in using the SCATTER instruction. Client objects to cstEmployee are then free to be constructed only having to know about these queries.

Like I said, the wrapper class notion has a lot of merit.

Larry
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform