|
-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Voris, John
Typically, we worked around this sort of problem in the past by
immediately storing the global fields in a work variable . .
Buck is right on! This is what I also try to do, and I don't
mind creating work variables that I will use later for the
action that I really want to do. Once I decide what "action"
I am going to do, I try to direct the action in it's own
module. Let the actors in the play do what they need to do
to deliver their lines.
Most of the time, I don't worry that I am inefficient
doing several chains to the same record.
Attempt to get away from "getters"
Believe in the "Tell, Don't Ask" pattern.
http://www.pragprog.com/articles/tell-dont-ask
http://c2.com/cgi/wiki?TellDontAsk
"You should endeavor to tell objects what you want them to
do; Do not ask them questions about their state.
Make a decision, and then tell them what to do."
--
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.