which some-more appropriate: getters setters functions?


is ever suitable dried "getmyvalue()" "setmyvalue()" settlement getters setters choice duty names api some-more obvious?



for example, suspect i have category c++:




public category someclass {
private:
bool misvisible;

public:
vacant draw();
vacant erase();
}


i supplement functions get/set "misvisible" this:




bool getvisible() { relapse misvisible; };



void setvisible(bool visible) {
(!misvisible && visible) {
draw();
} else (misvisible && !visible) {
erase();
}



misvisible = visible;


}



however, equally illusory following methods instead:




bool isvisible() { relapse misvisible; };

void show() {
(!misvisible) {
misvisible = true;
draw();
}
}

void hide() {
(misvisible) {
misvisible = false;
erase();
}
}


in brief, improved have unparalleled "setvisible(bool)" method, camber "show()" "hide()" methods? there convention, definitely inequitable thing?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?