> 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 think it's like we are talking about a door; you would say;
"The door is open", but "The door is opened" would be OK too.
You would not say "The door is close", you'd want to say "the door is
closed".
Not least because "the door is close" is ambiguous (when he wrote that,
did he mean the door is closed, or that the door is near by?)
The same holds for select/selected here, and we should say selected
(though I don't think "the door is slected" makes that much sense as an
example usage...)
So, I'd opt for:
is_open()
is_closed()
is_selected()
Just my tuppence worth. IANAELM [1].
--
Ian
[1] I Am Not An English Language Major...
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
