Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
To Class or not to class
Message
From
10/04/2018 15:59:25
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
 
To
10/04/2018 13:51:15
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01659269
Message ID:
01659300
Views:
59
The other advantage to Tamar's observation about separate prg out of one big prg or class, is maintenance. In a huge app that calls a function that could be anywhere or has code in a class you can't view while there's an object based on it, code inside other prgs or deeply embedded objects is a recipe for author indispensability because it can take anybody else hours to pick through with Gofish or traversing documentation trying to track down the culprit code. Whereas if it's in its own prg, it's directly accessible in project manager. FWIW I spent about a month out of the last 12 ripping stuff out of methods and massive "Set Procedure" prgs into linear files for this exact reason: now you can maintain/edit something in seconds that used to involve as much as 10 minutes just trying to track down/trace what's going on.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Previous
Reply
Map
View

Click here to load this message in the networking platform