-
Notifications
You must be signed in to change notification settings - Fork 1
/
sigslot_test.cpp
135 lines (124 loc) · 5.24 KB
/
sigslot_test.cpp
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
// sigslot.h: Signal/Slot classes
//
// Written by Sarah Thompson ([email protected]) 2002.
//
// License: Public domain. You are free to use this code however you like, with the proviso that
// the author takes on no responsibility or liability for any use.
//
// QUICK DOCUMENTATION
//
// (see also the full documentation at http://sigslot.sourceforge.net/)
//
// #define switches
// SIGSLOT_PURE_ISO - Define this to force ISO C++ compliance. This also disables
// all of the thread safety support on platforms where it is
// available.
//
// SIGSLOT_USE_POSIX_THREADS - Force use of Posix threads when using a C++ compiler other than
// gcc on a platform that supports Posix threads. (When using gcc,
// this is the default - use SIGSLOT_PURE_ISO to disable this if
// necessary)
//
// SIGSLOT_DEFAULT_MT_POLICY - Where thread support is enabled, this defaults to multi_threaded_global.
// Otherwise, the default is single_threaded. #define this yourself to
// override the default. In pure ISO mode, anything other than
// single_threaded will cause a compiler error.
//
// PLATFORM NOTES
//
// Win32 - On Win32, the WIN32 symbol must be #defined. Most mainstream
// compilers do this by default, but you may need to define it
// yourself if your build environment is less standard. This causes
// the Win32 thread support to be compiled in and used automatically.
//
// Unix/Linux/BSD, etc. - If you're using gcc, it is assumed that you have Posix threads
// available, so they are used automatically. You can override this
// (as under Windows) with the SIGSLOT_PURE_ISO switch. If you're using
// something other than gcc but still want to use Posix threads, you
// need to #define SIGSLOT_USE_POSIX_THREADS.
//
// ISO C++ - If none of the supported platforms are detected, or if
// SIGSLOT_PURE_ISO is defined, all multithreading support is turned off,
// along with any code that might cause a pure ISO C++ environment to
// complain. Before you ask, gcc -ansi -pedantic won't compile this
// library, but gcc -ansi is fine. Pedantic mode seems to throw a lot of
// errors that aren't really there. If you feel like investigating this,
// please contact the author.
//
//
// THREADING MODES
//
// single_threaded - Your program is assumed to be single threaded from the point of view
// of signal/slot usage (i.e. all objects using signals and slots are
// created and destroyed from a single thread). Behaviour if objects are
// destroyed concurrently is undefined (i.e. you'll get the occasional
// segmentation fault/memory exception).
//
// multi_threaded_global - Your program is assumed to be multi threaded. Objects using signals and
// slots can be safely created and destroyed from any thread, even when
// connections exist. In multi_threaded_global mode, this is achieved by a
// single global mutex (actually a critical section on Windows because they
// are faster). This option uses less OS resources, but results in more
// opportunities for contention, possibly resulting in more context switches
// than are strictly necessary.
//
// multi_threaded_local - Behaviour in this mode is essentially the same as multi_threaded_global,
// except that each signal, and each object that inherits has_slots, all
// have their own mutex/critical section. In practice, this means that
// mutex collisions (and hence context switches) only happen if they are
// absolutely essential. However, on some platforms, creating a lot of
// mutexes can slow down the whole OS, so use this option with care.
//
// USING THE LIBRARY
//
// See the full documentation at http://sigslot.sourceforge.net/
//
//
// sigslot.hpp : head file
//
// Version 1.0
//
// Copyright (c) 2020 NauhWuun, All Rights Reserved.
//
/////////////////////////////////////////////////////////////////////////////
//****************************************************************************
//****************************************************************************
// Update History
//
// Version 1.0, 2021-1-11
// -First Release
//****************************************************************************
#include <sigslot.hpp>
using namesapce sigslot;
struct Sender
{
Synapse::sigslot::signals<std::string, int> signalSender;
void help1() {
signalSender("Help1", 1);
}
void help2() {
signalSender("Help2", 2);
}
};
struct Receiver :public Synapse::sigslot::has_slots
{
void onReceiver(std::string message, int type)
{
cout << message << endl;
if (type == 1) {
std::cout << "correct slot" << std::endl;
}
else {
std::cout << "wrong slot" << std::endl;
}
}
};
int main()
{
Sender sender;
Receiver rec;
sender.signalSender.connect(&rec, &Receiver::onReceiver);
sender.help1();
sender.help2();
sender.signalSender.disconnect(&rec);
}