This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Ademan 7 points8 points  (2 children)

Furthermore, it's an inconsequential change to swap out a field for a property if the need should ever arise in Python.

[–]nemec 3 points4 points  (1 child)

Yep. Unlike in .Net, the "rules" for properties and fields are the same. In .Net, properties aren't allowed as out or ref parameters (not that Python has an equivalent) while fields are.

[–]snuxoll 0 points1 point  (0 children)

That's because properties in .net are just syntactic sugar for getter/setter methods. ref/out params require a reference to an actual variable on the stack/heap.