I strongly agree with JLee here
"code that runs stable once, should run stable in future (while nothing has
changed in the environment)"
Improvements and performance enhancements are always welcomed but they
should not break existing code. Google breaks code all the time, it's true,
and it's horr
@SRI
it's a question of definition (and point of view), what improvement/progress
is, and if refactoring code is the "cost" we have to accept for it.
I have to manage a huge project with a relativ high level of complexity.
Refactoring code, depending on what has to be refactored, can cost me
hou
> For me, it would be acceptable, if I could get backward-compatibility by
> setting a flag
*
> (e.g. on project-level)
*
> .
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Since-4-8-0-1-SIGSEGV-on-accessing-IEditable-from-ITextWatcher-s-AfterTextChange-tp571
非常感谢您的回答，非常抱歉浪费你的时间去阅读我的中国式英语
Thank you for your answer, very sorry to waste your time to read my
Chinese-style English
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/How-to-stop-SMS-broadcasting-tp5713474p5713502.html
Sent from the Mono for Android mailing list
