Cppcheck report - LibreOffice 2020-06-13 19:58:00 41c465b5ee443ec04441077b5eb80f263336ea8a, CppCheck 2020-06-13 18:19:47 6d5d12f283cf568d2dfe09aa77cb41f34b322d62: sc/qa/unit/functions_test.hxx

/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
/*
 * This file is part of the LibreOffice project.
 *
 * This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/.
 */

#include <sal/config.h>
#include <sal/types.h>

#include <unotest/filters-test.hxx>
#include "helper/qahelper.hxx"

#include <com/sun/star/uno/Reference.hxx>

class SCQAHELPER_DLLPUBLIC FunctionsTest : public ScBootstrapFixture, public test::FiltersTest
{
public:

    FunctionsTest(const OUString& rPath);
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
<--- Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. [+]
Class 'FunctionsTest' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.

    virtual void setUp() override;

    virtual bool load(
        const OUString &rFilter,
        const OUString &rURL,
        const OUString &rUserData,
        SfxFilterFlags nFilterFlags,
        SotClipboardFormatId nClipboardID,
        unsigned int nFilterVersion) override;

private:
    css::uno::Reference<css::uno::XInterface> m_xCalcComponent;
};

/* vim:set shiftwidth=4 softtabstop=4 expandtab: */