https://llvm.org/bugs/show_bug.cgi?id=30924
Bug ID: 30924
Summary: output when breaking comments is not stable
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: lec...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Classification: Unclassified
I'm using the llvm style and clang-format-4.0
The code i'm using for this test is the following :
struct foo {
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to keep my codebase coherent. make it loooooong
int32_t foobar; ///< Antoher member
};
After the first run :
struct foo {
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to keep my codebase
///coherent. make it loooooong
int32_t foobar; ///< Antoher member
};
After the second run :
struct foo {
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to keep my codebase
/// coherent. make it loooooong
int32_t foobar; ///< Antoher member
};
You can notice the "///coherent" became "/// coherent"
------
Another (similar) issue with this when it breaks on more than once :
original code :
struct foo {
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to keep my codebase coherent. make it
looooooooooooooooooooooooo oooooooooooooooooooooooo ooooooooooooooooooooo
oooooooooong
int32_t foobar; ///< Antoher member
};
After the first run :
struct foo
{
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to
///keep my codebase coherent. make it
looooooooooooooooooooooooo
///oooooooooooooooooooooooo ooooooooooooooooooooo
oooooooooong
int32_t foobar; ///< Antoher member
};
After the second run :
struct foo
{
int32_t foo; ///< awesome member documentation
int32_t bar; ///< Some really long comment for doxygen that I still want
after the member to
/// keep my codebase coherent. make it
looooooooooooooooooooooooo
/// oooooooooooooooooooooooo ooooooooooooooooooooo oooooooooong
int32_t foobar; ///< Antoher member
};
As you can see the 3rd line of comment is not aligned with the previous ones
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
