Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
OpenDAS
dlib
Commits
7e8af32b
Commit
7e8af32b
authored
Jun 08, 2011
by
Davis King
Browse files
Clarified spec and docs
parent
384090c6
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
7 deletions
+7
-7
dlib/threads/thread_pool_extension_abstract.h
dlib/threads/thread_pool_extension_abstract.h
+4
-4
docs/docs/api.xml
docs/docs/api.xml
+3
-3
No files found.
dlib/threads/thread_pool_extension_abstract.h
View file @
7e8af32b
...
@@ -219,10 +219,10 @@ namespace dlib
...
@@ -219,10 +219,10 @@ namespace dlib
a thread_pool thread capable of executing tasks.
a thread_pool thread capable of executing tasks.
This object is also implemented such that no memory allocations occur
This object is also implemented such that no memory allocations occur
after the thread
pool has been constructed
(the future object also
after the thread
_
pool has been constructed
so long as the user doesn't
doesn't perform any memory allocations or contain any system
call any of the add_task_by_value() routines. The future object also
resources such as mutex objects) so long as the user doesn't call
doesn't perform any memory allocations or contain any system resources
any of the add_task_by_value() routine
s.
such as mutex object
s.
EXCEPTIONS
EXCEPTIONS
Note that if an exception is thrown inside a task thread and
Note that if an exception is thrown inside a task thread and
...
...
docs/docs/api.xml
View file @
7e8af32b
...
@@ -1167,9 +1167,9 @@
...
@@ -1167,9 +1167,9 @@
The implementation of this extension can be found
The implementation of this extension can be found
<a
href=
"dlib/threads/thread_pool_extension.h.html"
>
here
</a>
. It is
<a
href=
"dlib/threads/thread_pool_extension.h.html"
>
here
</a>
. It is
implemented such that no memory allocations occur after the thread pool
implemented such that no memory allocations occur after the thread pool
has been constructed
(the future object also doesn't perform any memory allocations or contain any system
has been constructed
so long as the user doesn't call
resources such as mutex objects) so long as the user
doesn't
call
any of the add_task_by_value() routines. The future object also
doesn't
any of the add_task_by_value() routine
s.
perform any memory allocations or contain any system resources such as mutex object
s.
</description>
</description>
<examples>
<examples>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment