lumiera_/tests/basics/visitingtool-test.cpp
Ichthyostega 806db414dd Copyright: clarify and simplify the file headers
* Lumiera source code always was copyrighted by individual contributors
 * there is no entity "Lumiera.org" which holds any copyrights
 * Lumiera source code is provided under the GPL Version 2+

== Explanations ==
Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above.
For this to become legally effective, the ''File COPYING in the root directory is sufficient.''

The licensing header in each file is not strictly necessary, yet considered good practice;
attaching a licence notice increases the likeliness that this information is retained
in case someone extracts individual code files. However, it is not by the presence of some
text, that legally binding licensing terms become effective; rather the fact matters that a
given piece of code was provably copyrighted and published under a license. Even reformatting
the code, renaming some variables or deleting parts of the code will not alter this legal
situation, but rather creates a derivative work, which is likewise covered by the GPL!

The most relevant information in the file header is the notice regarding the
time of the first individual copyright claim. By virtue of this initial copyright,
the first author is entitled to choose the terms of licensing. All further
modifications are permitted and covered by the License. The specific wording
or format of the copyright header is not legally relevant, as long as the
intention to publish under the GPL remains clear. The extended wording was
based on a recommendation by the FSF. It can be shortened, because the full terms
of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00

153 lines
3.8 KiB
C++
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/*
VisitingTool(Test) - check the standard visitor use case
Copyright (C)
2008, Hermann Vosseler <Ichthyostega@web.de>
  **Lumiera** is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License as published by the
  Free Software Foundation; either version 2 of the License, or (at your
  option) any later version. See the file COPYING for further details.
* *****************************************************************/
/** @file visitingtool-test.cpp
** unit test \ref VisitingTool_test
*/
#include "lib/test/run.hpp"
#include "lib/visitor.hpp"
#include "lib/format-string.hpp"
#include <iostream>
using util::_Fmt;
using std::string;
using std::cout;
namespace lib {
namespace visitor {
namespace test1 {
typedef visitor::Tool<> VisitingTool;
class HomoSapiens : public Visitable<>
{
public:
DEFINE_PROCESSABLE_BY (VisitingTool);
};
class Boss : public HomoSapiens
{
public:
DEFINE_PROCESSABLE_BY (VisitingTool);
};
class BigBoss : public Boss
{
public:
DEFINE_PROCESSABLE_BY (VisitingTool);
};
class Visionary : public Boss
{
DEFINE_PROCESSABLE_BY (VisitingTool);
};
class Leader : public Visionary
{
};
class VerboseVisitor
: public VisitingTool
{
protected:
void talk_to (string guy)
{
cout << _Fmt{"Hello %s, nice to meet you...\n"} % guy;
}
};
class Babbler
: public Applicable< Babbler
, Types<Boss,BigBoss,Visionary>::List // dispatch calls to this types
, VerboseVisitor
>
{
public:
void treat (Boss&) { talk_to("Boss"); }
void treat (BigBoss&) { talk_to("Big Boss"); }
};
// note the following details:
// - Babbler "forgot" to declare being applicable to HomoSapiens
// - we have new derived class Leader without separate "apply()"-implementation
/*********************************************************************//**
* @test our lib implementation of the visitor pattern.
* Defines a hierarchy of test classes to check the following cases
* - calling the correct visiting tool specialised function
* for given concrete hierarchy classes
* - visiting tool not declaring to visit some class
* is silently ignored by default
* - newly added classes will be handled by existing
* functions according to inheritance relations
*/
class VisitingTool_test : public Test
{
virtual void
run (Arg)
{
known_visitor_known_class();
visiting_extended_hierarchy();
}
void
known_visitor_known_class()
{
Boss x1;
BigBoss x2;
// masquerade as HomoSapiens...
HomoSapiens& homo1 (x1);
HomoSapiens& homo2 (x2);
cout << "=== Babbler meets Boss and BigBoss ===\n";
Babbler bab;
VisitingTool& vista (bab);
homo1.apply (vista);
homo2.apply (vista);
}
void
visiting_extended_hierarchy()
{
HomoSapiens x1;
Leader x2;
HomoSapiens& homo1 (x1);
HomoSapiens& homo2 (x2);
cout << "=== Babbler meets HomoSapiens and Leader ===\n";
Babbler bab;
VisitingTool& vista (bab);
homo1.apply (vista); // silent error handler (not Applicable to HomoSapiens)
homo2.apply (vista); // Leader handled as Visionary and treated as Boss
}
};
/** Register this test class... */
LAUNCHER (VisitingTool_test, "unit common");
}}} // namespace lib::visitor::test1