Re: How far to push behavioural compatibility with native?
wrote: > A) Bug compatibility => Behavioural compatibility => drop existing >code and try to mimic native's behaviour as closely as possible. > B) PAUSE and RESUME is a useful extension not present in native, keep it >as long as no app is affected by this difference in behaviour. A basic rule is to change existing behaviour only if there is an app that depends on it. In other words: if there is no bug - there is nothing to fix. -- Dmitry.
Re: How far to push behavioural compatibility with native?
On 8 July 2010 10:32, wrote: > What do you think? > A) Bug compatibility => Behavioural compatibility => drop existing > code and try to mimic native's behaviour as closely as possible. > B) PAUSE and RESUME is a useful extension not present in native, keep it > as long as no app is affected by this difference in behaviour. Bug-for-bug compatibility with an explanatory note somewhere (wiki page "BrokenByDesign"?) as to why. Now you have to write a test for it, of course ... "Fail! Your MIDI works!" - d.
