On Thu, Oct 7, 2010 at 5:49 AM, JMGross <[email protected]> wrote:
> Thanks for all your work (even if I don't use mspgcc4 as it isn't ready for
> critical production environment)
>
You're welcome. But:
In case somebody reads this and decides to avoid mspgcc4 in favor of a
supposedly production-ready mspgcc3, the parameter non-truncation problem
Kim Toms found seems to be present there too. The difference? Nobody's
going to fix it in mspgcc3.
None of this stuff is what I would call ready for a critical production
environment. If you've been using something for years, and have hand-coded
around the problems and limitations that you've found affect your current
code, there's little motivation to move to a new version that may have new
problems to discover. But don't assume that's an indication of quality from
an independent perspective, or that there aren't things going wrong that you
just haven't found yet.
Dealing with updates is a pain, but I've found that in general the overall
quality improves with time. Problems you identify help somebody else, and
vice-versa. The tragedy of the commons applies very nicely in open source
development.
Peter
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
