/usr/include/corelinux/Bridge.hpp is in libcorelinux-dev 0.4.32-7.4ubuntu1.
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 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 | #if !defined (__BRIDGE_HPP)
#define __BRIDGE_HPP
/*
CoreLinux++
Copyright (C) 1999,2000 CoreLinux Consortium
The CoreLinux++ Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
The CoreLinux++ Library Library 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
Library General Public License for more details.
You should have received a copy of the GNU Library General Public
License along with the GNU C Library; see the file COPYING.LIB. If not,
write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA.
*/
#if !defined(__COMMON_HPP)
#include <Common.hpp>
#endif
namespace corelinux
{
/**
When an abstraction can have one of several possible implementations,
the usual way to accommodate them is to use inheritance. An abstract
class defines the interface to the abstraction, and concrete subclasses
implement it in different ways. But this approach isn't always flexible
enough. Inheritance binds an implementation to the abstraction permanently,
which makes it difficult to modify, extend, and reuse abstractions and
implementations independently. A Bridge decouples an abstraction from
its implementation so that the two can vary independently.
*/
template <class Implementation>
class Bridge : public CoreLinuxObject
{
public:
/**
Default Constructor requires a Implementation
@param Implementation instance
*/
Bridge( Implementation aImplementation )
:
CoreLinuxObject(),
theImplementation(aImplementation)
{
; // do nothing
}
/// Virtual Destructor
virtual ~Bridge( void )
{
; // do nothing
}
//
// Operator overloads
//
/**
Assignment operator overload. This may throw
Exception if there is a problem cloning theImplementation.
@param Bridge const reference
@return Bridge reference to self
@exception Exception - implementation defined
*/
Bridge & operator=( const Bridge & aRef ) throw(Exception)
{
this->setImplementation( aRef.getImplementation() );
return (*this);
}
/**
Equality operator overload
@param Bridge const reference
@return true if equal, false otherwise
*/
bool operator==( const Bridge & ) const
{
return (this == &aRef);
}
/**
Non-equality operator overload
@param Bridge const reference
@return false if equal, true otherwise
*/
bool operator!=( const Bridge & ) const
{
return !(*this == aRef);
}
protected:
/** Default Constructor
Because a Bridge requires a implementation
to work, you can not construct one without it.
@param void
@exception NEVER_GET_HERE
*/
Bridge( void ) throw (Assertion)
{
NEVER_GET_HERE;
}
/** Copy Constructor
Because theImplementation is owned by
the Bridge, only the assignment operator
insures that the derivation is constructed
and can be invoked for object management.
@param Bridge const reference
@exception NEVER_GET_HERE
*/
Bridge( const Bridge & ) throw (Assertion)
{
NEVER_GET_HERE;
}
//
// Accessors
//
/**
Gets current theImplementation
@return Implementation instance
*/
Implementation getImplementation( void ) const
{
return theImplementation;
}
//
// Mutators
//
/**
Set theImplementation. This in turn calls the pure-virtual
method cloneImplementation so that a pointer unique to this
object, or one which is referencable can be managed
@param Implementation instance
@exception Exception - implementation defined
*/
void setImplementation( Implementation aImpl ) throw(Exception)
{
theImplementation = cloneImplementation(aImpl);
}
/**
Pure virtual method to have the derivation contain
theImplementation.by ownership.
@param Implementation instance
@return Implementation instance
@exception Exception - implementation defined
*/
virtual Implementation cloneImplementation
(
Implementation
) throw(Exception) = 0;
private:
/// Storage for theImplementation object
Implementation theImplementation;
};
}
#endif // if !defined(__BRIDGE_HPP)
/*
Common rcs information do not modify
$Author: prudhomm $
$Revision: 1.1 $
$Date: 2000/04/23 20:43:13 $
$Locker: $
*/
|