René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Confusing Variable class names used for different purposes","articleBody":"After spending quite many hours in the codebase, there is one thing I find really confusing and time consuming: Some classes are named the same thing, but with different functions. Applies to `Variable` and partly to `Array` and `Record`. \r\n\r\n```py\r\n    variable.Variable\r\n    pdo.base.Variable  # Inherited from variable.Variable\r\n    sdo.base.Variable  # Inherited from variable.Variable\r\n    objectdictionary.Variable\r\n```\r\n\r\nI understand the functions for all of these. and I get it if the intention was to make a duck-type like class, but they're really not all compatible. It does not help that type checkers and linters often displays the base name of the class, not the full path. If the type checker report an error where it expects `Variable`, a small investigation is required to figure out which of these classes is the one that should be used.\r\n\r\nI would like to suggest to change the class names into unique names as follows:\r\n\r\n```py\r\n    class Variable:  # in variable.py\r\n    class PdoVariable(Variable):\r\n    class SdoVariable(Variable):\r\n    class ODVariable:\r\n```\r\nLikewise for `Array` into `class SdoArray` and `class ODArray`, and `Record` into `class SdoRecord` and `class ODRecord`. I don't intend any changes to the methods and the class inheritance. If we need to keep the old names intact for compatibility, we can do so as aliases in the respective files. I can spin up a PR if there's interest for this.","author":{"url":"https://github.com/sveinse","@type":"Person","name":"sveinse"},"datePublished":"2023-04-06T22:55:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/363/canopen/issues/363"}