On 9/23/24 22:51, Dan Sommers via Python-list wrote:
On 2024-09-23 at 19:00:10 +0100,
Barry Scott <barry@barrys-emacs.org> wrote:
On 21 Sep 2024, at 11:40, Dan Sommers via Python-list <python-list@python.org> wrote:
But once your code gets big the disciple of using classes helps
maintenance. Code with lots of globals is problematic.
Even before your code gets big, discipline helps maintenance. :-)
Every level of your program has globals. An application with too many classes is no better (or worse) than a class with too many methods, or a module with too many functions. Insert your own definitions of (and tolerances for) "too many," which will vary in flexibility.
I think the need of classes comes when you need objects thus a set of variables with an identity and that may be created N times. Classes are
object factories.
A second aspect is inheritance: classes may inherit from other classes
and reuse existing functionality and data structures for their objects.
In cases where you only need to encapsulate a single set of data and
functions modules are the best choice.
--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)