http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/ Just another Blog.mozilla.com weblog Wed, 11 Nov 2009 17:56:44 -0800 http://wordpress.org/?v=2.8.6 hourly 1 http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/comment-page-1/#comment-8092 tglek Tue, 04 Dec 2007 16:54:07 +0000 http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/#comment-8092 SK, There is an infinite amount of stuff to do :) Feel free to contribute. SK,
There is an infinite amount of stuff to do
Feel free to contribute.

]]> http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/comment-page-1/#comment-8090 SK Tue, 04 Dec 2007 16:52:08 +0000 http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/#comment-8090 I am new to deCOMtamination, but would like to contribute. I was just wondering if it is worth working on deCOMtamination bugs listed in Mozilla wiki or just wait for you guys to complete this effort. Once you complete these tools, will they automatically fix 90% of these bugs? I am new to deCOMtamination, but would like to contribute. I was just wondering if it is worth working on deCOMtamination bugs listed in Mozilla wiki or just wait for you guys to complete this effort. Once you complete these tools, will they automatically fix 90% of these bugs?

]]> http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/comment-page-1/#comment-3643 tglek Tue, 11 Sep 2007 04:29:09 +0000 http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/#comment-3643 James, That's a todo item that we have to formalize too. We have to decide which parts of the 'standard C++' are safe to use. For example turns out C++ strings are really inefficient in the receive MSVC++, so it doesn't seem like it makes sense to switch to them. James,
That’s a todo item that we have to formalize too. We have to decide which parts of the ’standard C++’ are safe to use.
For example turns out C++ strings are really inefficient in the receive MSVC++, so it doesn’t seem like it makes sense to switch to them.

]]> http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/comment-page-1/#comment-3640 James Napolitano Tue, 11 Sep 2007 04:03:40 +0000 http://blog.mozilla.com/tglek/2007/09/10/automatic-decomtamination-roadmap-for-automated-refactorings/#comment-3640 What about changing Mozilla from using NSPR to standard C++? What about changing Mozilla from using NSPR to standard C++?

]]>