Talk:Instance variable
It is of interest to the following WikiProjects:
Would it be more correct to say "... for which each object *of* the class has a separate copy"?
Not a paradigm
[edit ]No? Thebigclaw (talk) 04:23, 13 April 2008 (UTC) [reply ]
- I think the standard way to say this is "non-static member variable" but perhaps there is some subtle technical difference.66.112.225.87 (talk) 19:26, 21 August 2010 (UTC) [reply ]
Override has special meaning.
[edit ]At: However the current location referenced in one object may be San Francisco, USA, and you would want to override the default value to currLatitude = 37.7750, but another object may reference La Paz, Bolivia and you would instead want currLatitude = 16.4942. the term 'override' should not be used, as this has a special meaning in a number of OOP languages. It is also more technical than is required. 'change' is adequate.
However the current location referenced in one object may be San Francisco, USA, and you would want to change the default value to 37.7750. Another object may reference La Paz, Bolivia and you would want to change currLatitude to 16.4942. — Preceding unsigned comment added by 101.117.35.119 (talk) 01:01, 15 April 2014 (UTC) [reply ]
Not in Python
[edit ]What is returned by Google when searching for "instance variable" is the paragraph that says "a variable which is declared in a class but outside of constructors". However, that's not the case in Python where instance attributes are declared and initialised in the `__init__` method (e.g. just look at the given Python example).
Consequently, I find the above part of the definition misleading.
See also https://stackoverflow.com/questions/38377276/instance-variables-in-methods-outside-the-constructor-python-why-and-how Rhosseinkhan (talk) 07:27, 15 May 2025 (UTC) [reply ]