On Tue, 21 Nov 2000, Mike Nordell wrote:
> Misery. :-(
>
> It's not up to speed, though that code would temporary fix my problem for
> 0.7.12, but I'm not the one to give the call. However, my call is "Hold!",
> with a very visible exclamation mark behind it�. If we're working our a**es
> off to get a UCS-2, ASCII, Kanji and so forth relesee going, and then it
> turns out we can't even handle the C (since we're forbidden to use the C++
> locale) library in UI, wouldn't that make some users look at us like "what
> *are* these persons doing?"?
>
> So, how do we handle this. I'm in favor of a 0.7.12 release RSN, but on the
> other hand I know that a release somehow gets developers going on new stuff
> and sort of "forgets" about the earlier problems.
I don't think that this has to be the case ... especially if you
are willing to be the policeman reminding us about things not
really taken care of.
> I don't see this as a 0.7.12 showstopper, but it would be a stopper for .13
> or .14 since we know about it.
>
> Words anyone?
>
> Should we release a 0.7.12 with a known (hardcoded fix!) anomaly regarding
> floating point values in this very limited area, and then *require* that
> anyone ivolved in floating point display or parsing have a look at their
> current usage and if appropriate use what we decide upon, or should we
> simply hold 0.7.12?
I'm all in favour of a 0.7.12 release with the usual rough
edges ... goodness knows that the QNX interface has some
rough edges. I'm also waiting to make the list interface
dialog a little cleaner (in terms of implementation ...
it seems to me we have a lot of extra code there) until
after 0.7.12.
Thomas
-------------------------------------------------------------
Thomas (toe-mah) Fletcher QNX Software Systems
[EMAIL PROTECTED] Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf
