WebSocket++  0.8.3-dev
C++ websocket client/server library
functional.hpp
1 /*
2  * Copyright (c) 2014, Peter Thorson. All rights reserved.
3  *
4  * Redistribution and use in source and binary forms, with or without
5  * modification, are permitted provided that the following conditions are met:
6  * * Redistributions of source code must retain the above copyright
7  * notice, this list of conditions and the following disclaimer.
8  * * Redistributions in binary form must reproduce the above copyright
9  * notice, this list of conditions and the following disclaimer in the
10  * documentation and/or other materials provided with the distribution.
11  * * Neither the name of the WebSocket++ Project nor the
12  * names of its contributors may be used to endorse or promote products
13  * derived from this software without specific prior written permission.
14  *
15  * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
16  * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
17  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
18  * ARE DISCLAIMED. IN NO EVENT SHALL PETER THORSON BE LIABLE FOR ANY
19  * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
20  * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
21  * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
22  * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
23  * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
24  * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
25  *
26  */
27 
28 #ifndef WEBSOCKETPP_COMMON_FUNCTIONAL_HPP
29 #define WEBSOCKETPP_COMMON_FUNCTIONAL_HPP
30 
31 #include <websocketpp/common/cpp11.hpp>
32 
33 // If we've determined that we're in full C++11 mode and the user hasn't
34 // explicitly disabled the use of C++11 functional header, then prefer it to
35 // boost.
36 #if defined _WEBSOCKETPP_CPP11_INTERNAL_ && !defined _WEBSOCKETPP_NO_CPP11_FUNCTIONAL_
37  #ifndef _WEBSOCKETPP_CPP11_FUNCTIONAL_
38  #define _WEBSOCKETPP_CPP11_FUNCTIONAL_
39  #endif
40 #endif
41 
42 // If we're on Visual Studio 2010 or higher and haven't explicitly disabled
43 // the use of C++11 functional header then prefer it to boost.
44 #if defined(_MSC_VER) && _MSC_VER >= 1600 && !defined _WEBSOCKETPP_NO_CPP11_FUNCTIONAL_
45  #ifndef _WEBSOCKETPP_CPP11_FUNCTIONAL_
46  #define _WEBSOCKETPP_CPP11_FUNCTIONAL_
47  #endif
48 #endif
49 
50 
51 
52 #ifdef _WEBSOCKETPP_CPP11_FUNCTIONAL_
53  #include <functional>
54 #else
55  #include <boost/bind.hpp>
56  #include <boost/function.hpp>
57  #include <boost/ref.hpp>
58 #endif
59 
60 
61 
62 namespace websocketpp {
63 namespace lib {
64 
65 #ifdef _WEBSOCKETPP_CPP11_FUNCTIONAL_
66  using std::function;
67  using std::bind;
68  using std::ref;
69  namespace placeholders = std::placeholders;
70 
71  // There are some cases where a C++11 compiler balks at using std::ref
72  // but a C++03 compiler using boost function requires boost::ref. As such
73  // lib::ref is not useful in these cases. Instead this macro allows the use
74  // of boost::ref in the case of a boost compile or no reference wrapper at
75  // all in the case of a C++11 compile
76  #define _WEBSOCKETPP_REF(x) x
77 
78  template <typename T>
79  void clear_function(T & x) {
80  x = nullptr;
81  }
82 #else
83  using boost::function;
84  using boost::bind;
85  using boost::ref;
86  namespace placeholders {
87  /// \todo this feels hacky, is there a better way?
88  using ::_1;
89  using ::_2;
90  using ::_3;
91  }
92 
93  // See above definition for more details on what this is and why it exists
94  #define _WEBSOCKETPP_REF(x) boost::ref(x)
95 
96  template <typename T>
97  void clear_function(T & x) {
98  x.clear();
99  }
100 #endif
101 
102 } // namespace lib
103 } // namespace websocketpp
104 
105 #endif // WEBSOCKETPP_COMMON_FUNCTIONAL_HPP
websocketpp::versions_supported
static std::vector< int > const versions_supported(helper, helper+4)
Container that stores the list of protocol versions supported.