/**************************************************************************** ** ** Copyright (C) 2016 The Qt Company Ltd. ** Contact: https://www.qt.io/licensing/ ** ** This file is part of Qt Creator. ** ** Commercial License Usage ** Licensees holding valid commercial Qt licenses may use this file in ** accordance with the commercial license agreement provided with the ** Software or, alternatively, in accordance with the terms contained in ** a written agreement between you and The Qt Company. For licensing terms ** and conditions see https://www.qt.io/terms-conditions. For further ** information use the contact form at https://www.qt.io/contact-us. ** ** GNU General Public License Usage ** Alternatively, this file may be used under the terms of the GNU ** General Public License version 3 as published by the Free Software ** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT ** included in the packaging of this file. Please review the following ** information to ensure the GNU General Public License requirements will ** be met: https://www.gnu.org/licenses/gpl-3.0.html. ** ****************************************************************************/ #include "Overview.h" #include "NamePrettyPrinter.h" #include "TypePrettyPrinter.h" #include #include #include using namespace CPlusPlus; /*! \class Overview \brief The Overview class converts a FullySpecifiedType and/or any qualified name to its string representation. The public data members (except the ones starting with \e marked) determine what exactly and how to print. You can get the start and end position of a function argument in the resulting string. Set \c markedArgument to the desired argument. After processing, \c markedArgumentBegin and \c markedArgumentEnd will contain the positions. */ /*! \enum Overview::StarBindFlag The StarBindFlag enum describes how the '*' and '&' in pointers/references should be bound in the string representation. This also applies to rvalue references ('&&'), but not to pointers to functions or arrays, because it seems to be quite uncommon to use spaces in them. For example: \code void (*p)() void (*p)[] \endcode See the examples below. These assume that exactly one flag is set. That is, it may look different with flag combinations. \value BindToIdentifier e.g. "char *foo", but not "char * foo" \value BindToTypeName e.g. "char*", but not "char *" \value BindToLeftSpecifier e.g. "char * const* const", but not "char * const * const" \value BindToRightSpecifier e.g. "char *const", but not "char * const" */ Overview::Overview() : starBindFlags(BindToIdentifier), // default to "Qt Style" showArgumentNames(false), showReturnTypes(false), showFunctionSignatures(true), showDefaultArguments(true), showTemplateParameters(false), showEnclosingTemplate(false), includeWhiteSpaceInOperatorName(true), markedArgument(0), markedArgumentBegin(0), markedArgumentEnd(0) { } QString Overview::prettyName(const Name *name) const { NamePrettyPrinter pp(this); return pp(name); } QString Overview::prettyName(const QList &fullyQualifiedName) const { QString result; const int size = fullyQualifiedName.size(); for (int i = 0; i < size; ++i) { result.append(prettyName(fullyQualifiedName.at(i))); if (i < size - 1) result.append(QLatin1String("::")); } return result; } QString Overview::prettyType(const FullySpecifiedType &ty, const Name *name) const { return prettyType(ty, prettyName(name)); } QString Overview::prettyType(const FullySpecifiedType &ty, const QString &name) const { TypePrettyPrinter pp(this); return pp(ty, name); }