"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
Again, I'm sorry. Emphasis is on _implementation_. This is an
implementation _by a Windows user for Windows users_ that doesn't
suck too terribly for traditional users (and some traditional users
will like).
So what's the problem?
However, as far as I can tell after some experimentation, the
correct way to document it for traditional users is "Expect
anomalies; we don't know what this code does in many circumstances.
Mostly it does the right thing; you'll get used to it."
Is that really acceptable to you?
It might be, except I don't really understand what it means. What
does "we don't know" mean? "We're too lazy to look it up?"
"The code
is written badly so we cannot understand it?" There's a difference
between the two.
Therefore the default action, absent a thorough fix, is "the
code
comes out."
This is not true. The code is tested and works well; if you want to
remove it, you get to prove why you want to do so. Those are the
rules of the game.
Also note that you haven't named a single actual flaw the code has.
Before you do, how can you hope that anyone will "fix" it?
Since there is support for the implementation, I will move it to the
new devel branch which will open shortly, unless I see a consensus
of the Review Board in favor of putting it in the release.
Please don't attempt to do that. Please don't ignore vetos.