| /dports/emulators/mess/mame-mame0226/3rdparty/asio/src/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
75 [section Automatic deduction of initiating function return type]
77 The return type of an initiating function is `typename
87 [section Production of initiating function return value]
89 An initiating function produces its return type as follows:
115 For convenience, initiating functions may be implemented using the
133 [section Lifetime of initiating function arguments]
153 [section Non-blocking requirements on initiating functions]
187 argument to the initiating function.
[all …]
|
| /dports/emulators/mame/mame-mame0226/3rdparty/asio/src/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
75 [section Automatic deduction of initiating function return type]
77 The return type of an initiating function is `typename
87 [section Production of initiating function return value]
89 An initiating function produces its return type as follows:
115 For convenience, initiating functions may be implemented using the
133 [section Lifetime of initiating function arguments]
153 [section Non-blocking requirements on initiating functions]
187 argument to the initiating function.
[all …]
|
| /dports/multimedia/obs-websocket/obs-websocket-4.8.0/deps/asio/asio/src/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
75 [section Automatic deduction of initiating function return type]
77 The return type of an initiating function is `typename
87 [section Production of initiating function return value]
89 An initiating function produces its return type as follows:
115 For convenience, initiating functions may be implemented using the
133 [section Lifetime of initiating function arguments]
153 [section Non-blocking requirements on initiating functions]
187 argument to the initiating function.
[all …]
|
| /dports/devel/boost-docs/boost_1_72_0/libs/asio/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
71 [heading Automatic deduction of initiating function return type]
73 The return type of an initiating function is `typename
81 [heading Production of initiating function return value]
83 An initiating function produces its return type as follows:
109 For convenience, initiating functions may be implemented using the
125 [heading Lifetime of initiating function arguments]
143 [heading Non-blocking requirements on initiating functions]
173 argument to the initiating function.
[all …]
|
| /dports/www/restbed/restbed-4.8/dependency/asio/asio/src/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
71 [heading Automatic deduction of initiating function return type]
73 The return type of an initiating function is `typename
81 [heading Production of initiating function return value]
83 An initiating function produces its return type as follows:
109 For convenience, initiating functions may be implemented using the
125 [heading Lifetime of initiating function arguments]
143 [heading Non-blocking requirements on initiating functions]
173 argument to the initiating function.
[all …]
|
| /dports/devel/boost-libs/boost_1_72_0/libs/asio/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
71 [heading Automatic deduction of initiating function return type]
73 The return type of an initiating function is `typename
81 [heading Production of initiating function return value]
83 An initiating function produces its return type as follows:
109 For convenience, initiating functions may be implemented using the
125 [heading Lifetime of initiating function arguments]
143 [heading Non-blocking requirements on initiating functions]
173 argument to the initiating function.
[all …]
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/asio/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
71 [heading Automatic deduction of initiating function return type]
73 The return type of an initiating function is `typename
81 [heading Production of initiating function return value]
83 An initiating function produces its return type as follows:
109 For convenience, initiating functions may be implemented using the
125 [heading Lifetime of initiating function arguments]
143 [heading Non-blocking requirements on initiating functions]
173 argument to the initiating function.
[all …]
|
| /dports/devel/hyperscan/boost_1_75_0/libs/asio/doc/requirements/ |
| H A D | asynchronous_operations.qbk | 18 An ['initiating function] is a function which may be called to start an
26 initiating function.
71 [heading Automatic deduction of initiating function return type]
73 The return type of an initiating function is `typename
81 [heading Production of initiating function return value]
83 An initiating function produces its return type as follows:
109 For convenience, initiating functions may be implemented using the
125 [heading Lifetime of initiating function arguments]
143 [heading Non-blocking requirements on initiating functions]
173 argument to the initiating function.
[all …]
|
| /dports/databases/postgresql96-server/postgresql-9.6.24/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql96-plpython/postgresql-9.6.24/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql96-pltcl/postgresql-9.6.24/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-server/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-plperl/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-client/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-contrib/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-docs/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql10-plpython/postgresql-10.19/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-plperl/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-contrib/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-docs/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-plpython/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-server/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql11-client/postgresql-11.14/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql12-contrib/postgresql-12.9/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|
| /dports/databases/postgresql12-client/postgresql-12.9/src/backend/access/transam/ |
| H A D | README.parallel | 12 The backend which starts a parallel operation (hereafter, the initiating
16 messages reported via elog/ereport) from the worker back to the initiating
17 backend; (2) serialized representations of the initiating backend's private
18 state, so that the worker can synchronize its state with of the initiating
21 the initiating backend has initialized the dynamic shared memory segment, it
33 any failure of the background worker will not be reported to the initiating
35 failed to start. The initiating backend must anyway be prepared to cope
41 initiating backend. This causes the next CHECK_FOR_INTERRUPTS() in the
53 back to the initiating backend, the message will be lost altogether.)
112 (or the initiating backend) know about them.
[all …]
|