/usr/include/camp/valuevisitor.hpp is in libcamp0.7-dev 0.7.1.1-1ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 | /****************************************************************************
**
** Copyright (C) 2009-2010 TECHNOGERMA Systems France and/or its subsidiary(-ies).
** Contact: Technogerma Systems France Information (contact@technogerma.fr)
**
** This file is part of the CAMP library.
**
** CAMP is free software: you can redistribute it and/or modify
** it under the terms of the GNU Lesser General Public License as published by
** the Free Software Foundation, either version 3 of the License, or
** (at your option) any later version.
**
** CAMP is distributed in the hope that it will be useful,
** but WITHOUT ANY WARRANTY; without even the implied warranty of
** MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
** GNU Lesser General Public License for more details.
**
** You should have received a copy of the GNU Lesser General Public License
** along with CAMP. If not, see <http://www.gnu.org/licenses/>.
**
****************************************************************************/
#ifndef CAMP_VALUEVISITOR_HPP
#define CAMP_VALUEVISITOR_HPP
#ifndef Q_MOC_RUN
#include <boost/variant/static_visitor.hpp>
#endif
namespace camp
{
/**
* \brief Base class for writing custom Value visitors
*
* A value visitor acts like compile-time dispatchers which automatically
* calls the function which matches the actual type of the stored value.
* This is a more direct and straight-forward approach than using a runtime switch,
* based on value.type() and then converting to the proper type.
* It also gives access to enum and user objects, which can give useful informations with
* no knowledge about the actual C++ class or enum.
*
* The template parameter T is the type returned by the visitor.
*
* To handle one of the possible types of the value, just write the corresponding \c operator() function.
* Here is the list of the mapping between CAMP types and their corresponding C++ types:
*
* \li camp::noType --> camp::NoType
* \li camp::boolType --> bool
* \li camp::intType --> long
* \li camp::realType --> double
* \li camp::stringType --> std::string
* \li camp::enumType --> camp::EnumObject
* \li camp::userType --> camp::UserObject
*
* Here an example of a unary visitor which creates an editor for the value based on its type
* \code
* struct EditorFactory : public ValueVisitor<PropertyEditor*>
* {
* PropertyEditor* operator()(bool value)
* {
* return new BooleanEditor(value);
* }
*
* PropertyEditor* operator()(long value)
* {
* return new IntegerEditor(value);
* }
*
* PropertyEditor* operator()(double value)
* {
* return new RealEditor(value);
* }
*
* PropertyEditor* operator()(const std::string& value)
* {
* return new StringEditor(value);
* }
*
* PropertyEditor* operator()(const camp::EnumObject& value)
* {
* return new EnumEditor(value);
* }
*
* PropertyEditor* operator()(const camp::UserObject& value)
* {
* return new UserEditor(value);
* }
* };
*
* camp::Value value(5.4);
* PropertyEditor* editor = value.visit(EditorFactory());
* \endcode
*/
template <typename T = void>
class ValueVisitor : public boost::static_visitor<T>
{
};
} // namespace camp
#endif // CAMP_VALUEVISITOR_HPP
|