Apr-30-2017, 05:24 AM
(Apr-30-2017, 04:42 AM)Mekire Wrote: Though I think changes should still be made to make attributes clearer and there is no need to use that function to both set and get these attributes. As a C programmer I would think you would hate a function with an unpredictable return type.even in C i have made functions that set things and return the previous value for years. and then in cases where there is nothing being set, it just gets the current setting. so it's a get and set in one. i have been doing duck typing, even in C. i called it context typing.
i've seen the get/set combining in other source code, too. i've even seen cases where there being no way to not set a value, the caller set some value just to get the current value, then called again with what was returned to set it back. i think it was from my IBM mainframe assembler days.
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.