There's a lot of duplicated code in the webapp runtimes for mac, windows and unix. We should refactor it (this would avoid some problems, like bug 760747 or bug 761496).
To safely implement a refactoring to remove code duplication, I'd suggest landing unit test support in bug 733631 first. Then, implement this while adding unit tests in the process to catch regressions that may happen while refactoring.
We should also improve the error messages.
In general, I prefer to refactor in the process of fixing bugs or implementing enhancements rather than refactoring for its own sake, because it's hard to optimize for code maintainability (or other benefits of refactoring) without also doing some work that is made easier by the refactoring. Nevertheless, sometimes it's useful to isolate refactoring work, so I'm open to doing so. But it's hard to use a bug report to track a general refactoring; we'd need to know the specifics of what is to be refactored to be able to know what to do here. Marco: did you have any particular refactoring in mind?
I wanted to get rid of the duplicated code in gtk2/webapprt.cpp, win/webapprt.cpp and mac/webapprt.mm. But I think you're right, it's not worth the effort if you aren't modifying them for other purposes. Shall we close?
(In reply to Marco Castelluccio [:marco] from comment #4) > I wanted to get rid of the duplicated code in gtk2/webapprt.cpp, > win/webapprt.cpp and mac/webapprt.mm. > But I think you're right, it's not worth the effort if you aren't modifying > them for other purposes. > Shall we close? Yes, let's close this but keep that code duplication in mind as we make changes to those files in the future!