Skip to content

magic get/set methods #73

@GoogleCodeExporter

Description

@GoogleCodeExporter
Hi,

could you please replace these with just getters/setters or declare appropriate 
fields as protected?

The presence of magic get/set hides the real presence/absence of fields, thus 
accessing any not existent field from a derived class does not produce any 
errors. 

This increase debugging time significantly, while having regular 
getters/setters would be able to detect such issues during a few seconds

Thanks


Original issue reported on code.google.com by m...@mail.ru on 18 Sep 2013 at 10:08

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions