I agree that it did not belong in a feature-freeze phase. I'm sorry.
I didn't realize it would create such a problem (reminds me of substring ->
subString ha ha). There are however, valid reasons for changing the name, so
let's discuss after the release.
-
Cheers,
Sean
--
View this message
Do whatever you want, I have no more motivation to discuss this anymore
Ben
On 24 Jan 2014, at 14:34, Pharo4Stef wrote:
> Hi guys,
>
> I think that we will rename all the asReactiveVariable that got introduced
> into their old name asValueHolder.
> And we will rename the class too to its old
Hi guys,
I think that we will rename all the asReactiveVariable that got introduced into
their old name asValueHolder.
And we will rename the class too to its old name.
Why?
I think that we should not change at the last moment ValueHolder into
ReactiveVariable
even if the name could be better
