The difference in Python OOP between:
visually explained using ๐บ๐ฒ๐บ๐ผ๐ฟ๐_๐ด๐ฟ๐ฎ๐ฝ๐ต:
Coming from C++, I initially thought it aggravating that you have to go self. everywhere when working with classes in Python. But I've conceded that it improves code-legibility, and now I'm going this-> everywhere when I'm back in C++.
Another common naming convention in C++ is using an underscore as prefix for member variables: int _memberVariable{123};
My personal convention in C++ was to use an m prefix on member variables and a g for class variables.
I guess in Python, I think of _ as equivalent to protected scope in C++ and __ (double underscore) as equivalent to private. Not a perfect analogy, but it works for me.
Just don't use double underscores in C++, identifiers containing double underscores are reserved for the compiler/linker/standard library.
Same thing in Python, double underscore prefix triggers "name mangling". There are issues that can pop up when using it if not aware.
Welcome to the Python community on the programming.dev Lemmy instance!
Past
November 2023
October 2023
July 2023
August 2023
September 2023