https://bugs.documentfoundation.org/show_bug.cgi?id=172437
Bug ID: 172437
Summary: Research updating clang-format
Product: LibreOffice
Version: 26.8.0.0 alpha0+ master
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: difficultyBeginner, easyHack, skillCpp
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
At the moment we are using clang-format version 5.0.0 to format newly-added
files and to maintain the formatting in a selected group of files. The version
used is starting to show its age, for example
56e6d683dba66d4f2f80145064d2bda2ea4b27b1
"And then our venerable clang-format 5.0.0 would have broken the token `<=>`
into `<= >`, so exclude include/o3tl/compare.hxx from its mis-treatment."
The idea with this task is to research everything involved in updating
clang-format to match the Clang version we have as baseline (18 at the moment).
The main interesting thing is how big of a diff we get when reformatting
formatted files, but maybe there are other things no one anticipated.
https://wiki.documentfoundation.org/Development/clang-format
This should be done:
Assign the report to yourself.
Study everything within solenv/clang-format
Modify ClangFormat.pm so the wanted version is the new one.
Run the reformat-formatted-files script.
Check that everything still builds.
Create a commit with the changes.
Submit the patch as a work-in-progress with ./logerrit submit master%wip
Add the patch link in a comment here.
--
You are receiving this mail because:
You are the assignee for the bug.