Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
D
dlib
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
钟尚武
dlib
Commits
7e8af32b
Commit
7e8af32b
authored
Jun 08, 2011
by
Davis King
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarified spec and docs
parent
384090c6
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
7 deletions
+7
-7
thread_pool_extension_abstract.h
dlib/threads/thread_pool_extension_abstract.h
+4
-4
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
a thread_pool thread capable of executing tasks.
This object is also 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
resources such as mutex objects) so long as the user doesn't call
any of the add_task_by_value() routines.
after the thread
_pool has been constructed so long as the user doesn't
call any of the add_task_by_value() routines. The future object also
doesn't perform any memory allocations or contain any system resources
such as mutex objects.
EXCEPTIONS
Note that if an exception is thrown inside a task thread and
...
...
docs/docs/api.xml
View file @
7e8af32b
...
...
@@ -1167,9 +1167,9 @@
The implementation of this extension can be found
<a
href=
"dlib/threads/thread_pool_extension.h.html"
>
here
</a>
. It is
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
resources such as mutex objects) so long as the user doesn't call
any of the add_task_by_value() routines.
has been constructed
so long as the user doesn't call
any of the add_task_by_value() routines. The future object also doesn't
perform any memory allocations or contain any system resources such as mutex objects.
</description>
<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