1) Clang cannot compile all Qt-using codebases. Therefore, its tooling cannot work in all cases either. That's true, but on the other hand, covering at least a half of code bases would be a huge progress. I don't have representative statistics, but I guess that the real percentage will be larger.
2) No one has volunteered to write such conversion scripts Well, it could be a problem if there were no more or less commercially successful companies behind the Qt. There is a business value in such a tool. Of course providing porting as a service might bring more money, but it cannot be fully automated anyway. And a minor (3) is that automatic conversions seldom look nice and will require manual retouching anyway. Yes, sure. As I said before, it should be OK to automatically convert only the most straightforward cases and mark others. Even marking is already a very helpful thing. Vitaly ________________________________ From: Development <development-boun...@qt-project.org> on behalf of Thiago Macieira <thiago.macie...@intel.com> Sent: Thursday, April 23, 2020 15:55 To: development@qt-project.org <development@qt-project.org> Subject: [Development] Clang-based refactoring to Qt 6 (Proposal: Deprecate QVector in Qt 6) On Thursday, 23 April 2020 05:25:33 PDT Vitaly Fanaskov wrote: > Provide clang-based tools to (semi-)automatically port users' code bases to > a new version of Qt. These tools might either fix a code or at least add a > comment in potentially problematic places where a user should correct the > code. A developer who changes API should also implement a rule for these > tools. This was discussed in a QtCS two or three years ago. There are two huge problems with that: 1) Clang cannot compile all Qt-using codebases. Therefore, its tooling cannot work in all cases either. 2) No one has volunteered to write such conversion scripts. And a minor (3) is that automatic conversions seldom look nice and will require manual retouching anyway. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
