summaryrefslogtreecommitdiff
path: root/compilerplugins
diff options
context:
space:
mode:
authorAndrea Gelmini <andrea.gelmini@gelma.net>2020-04-28 17:19:13 +0200
committerAndrea Gelmini <andrea.gelmini@gelma.net>2020-04-30 10:31:29 +0200
commit7685dff381f538bf011a56da4a0493228b84614a (patch)
treec3fa9590d584af07bd940597b1183f1289b1864d /compilerplugins
parente4da8ae4bef37f5450dcf34d9f06b68e3b901c01 (diff)
Fix typos
Change-Id: I8d0e10b08393b7752d55298e0e1ba64e5fd6c422 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93083 Reviewed-by: Julien Nabet <serval2412@yahoo.fr> Tested-by: Jenkins
Diffstat (limited to 'compilerplugins')
-rw-r--r--compilerplugins/clang/test/cppunitassertequals.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/compilerplugins/clang/test/cppunitassertequals.cxx b/compilerplugins/clang/test/cppunitassertequals.cxx
index d0825000be07..d42007c99d66 100644
--- a/compilerplugins/clang/test/cppunitassertequals.cxx
+++ b/compilerplugins/clang/test/cppunitassertequals.cxx
@@ -53,7 +53,7 @@ void test(
CPPUNIT_ASSERT(t.operator ==(t));
// `P == nullptr` for P of pointer type is awkward to write with CPPUNIT_ASSERT_EQUAL, and the
- // actual pointer values that would be printed if CPPUNIT_ASSERT_EQUAL failed would likey not be
+ // actual pointer values that would be printed if CPPUNIT_ASSERT_EQUAL failed would likely not be
// very meaningful, so let it use CPPUNIT_ASSERT (but stick to CPPUNIT_ASSERT_EQUAL for
// consistency in the unlikely case that P is of type std::nullptr_t):
CPPUNIT_ASSERT(p == nullptr);