Added some comments regarding the use of std::swap.

--HG--
extra : convert_revision : svn%3Afdd8eb12-d10e-0410-9acb-85c331704f74/trunk%402816
This commit is contained in:
Davis King 2009-01-18 18:48:27 +00:00
parent 2299b24d2d
commit c02fd30aa1

View File

@ -148,7 +148,16 @@ int main()
dlog << LINFO << "Add job " << i << " to pipe"; dlog << LINFO << "Add job " << i << " to pipe";
job j; job j;
j.id = i; j.id = i;
// Add this job to the pipe. One of our three threads will get it and process it
// Add this job to the pipe. One of our three threads will get it and process it.
// It should also be pointed out that the enqueue() function uses the global
// swap function to move jobs into the pipe. This means that it modifies the
// jobs we are passing in to it. This allows you to implement a fast swap
// operator for your jobs. For example, std::vector objects have a global
// swap and it can execute in constant time by just swapping pointers inside
// std::vector. This means that the dlib::pipe is effectively a zero-copy
// message passing system if you setup global swap for your jobs.
pe.job_pipe.enqueue(j); pe.job_pipe.enqueue(j);
} }