I was noticing while creating the Fl_Tree API I had some second thoughts
about function naming.
Things like: open() / close() / select() / deselect() all seem obvious enough,
but when testing to see if something is selected, seemed one could go
either present or past tense:
is_open() vs. is_opened()
is_close() vs. is_closed()
is_select() vs. is_selected()
"is_open()" seemed right ("is the menu item open?")
"is_close()" seemed wrong ("is the menu close?"), but I went with that anyway,
because if I'd had "is_closed()" then people would expect "is_opened()". Shrug.
But "is_select()" sounded really wrong to me, so I went with "is_selected()".
Maybe that extra cup of coffee this morning is making me manic,
but I'm thinking some app programmer who got a better grade in english class
than I did will see this and say "wtf was he thinking; did he randomly add 'ed'
to some of these methods just to drive me insane?"
I can't tell if it's me encountering english language idiosyncrasies,
or if it's a personal preference I'll feel differently about tomorrow.
I guess it's too late to change now, but to avoid future madness,
is there something most folks agree on with this? I'd be curious..
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
