Cargando…
Effective modern C++ live! : Scott Meyers on void futures /
"What's the best way for one thread to notify another that an event has taken place? The traditional approach is to use a condition variable, but that requires a mutex, and for simple event communication, that seems like overkill: no data requires synchronized access. An alternative is to...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico Video |
| Idioma: | Inglés |
| Publicado: |
[Place of publication not identified] :
O'Reilly Media,
[2014]
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cgm a2200000Ii 4500 | ||
|---|---|---|---|
| 001 | OR_ocn913879974 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o c | ||
| 007 | cr cna|||||||| | ||
| 007 | vz czazuu | ||
| 008 | 150716s2015 xx 050 o vleng d | ||
| 040 | |a UMI |b eng |e rda |e pn |c UMI |d OCLCF |d UAB |d OCLCO | ||
| 035 | |a (OCoLC)913879974 | ||
| 037 | |a CL0500000614 |b Safari Books Online | ||
| 050 | 4 | |a QA76.73.C153 | |
| 049 | |a UAMI | ||
| 100 | 1 | |a Meyers, Scott |q (Scott Douglas), |e author. | |
| 245 | 1 | 0 | |a Effective modern C++ live! : |b Scott Meyers on void futures / |c with Scott Meyers. |
| 246 | 3 | |a Effective modern C plus plus live! | |
| 246 | 3 | 0 | |a Scott Meyers on void Futures |
| 264 | 1 | |a [Place of publication not identified] : |b O'Reilly Media, |c [2014] | |
| 264 | 4 | |c ©2014 | |
| 300 | |a 1 online resource (1 streaming video file (49 min., 42 sec.)) : |b digital, sound, color. | ||
| 336 | |a two-dimensional moving image |b tdi |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 500 | |a Title from title screen (Safari, viewed July 8, 2015). | ||
| 500 | |a Date of publication taken from slide 2 (Safari, viewed July 8, 2015). | ||
| 511 | 0 | |a Presenter, Scott Meyers. | |
| 520 | |a "What's the best way for one thread to notify another that an event has taken place? The traditional approach is to use a condition variable, but that requires a mutex, and for simple event communication, that seems like overkill: no data requires synchronized access. An alternative is to use a shared flag, but that requires polling on the part of the thread waiting for notification. As of C++ 11, an interesting new option is the use of a void future. Like the approach based on condition variables, the task waiting for notification truly blocks--no polling is required. Like the approach based on a shared flag, there's no need for a mutex. The approach even makes it possible for the notifying thread to throw an exception that the waiting-to-be-notified thread can catch. However, a design based on void futures has costs and is constrained by restrictions that developers must keep in mind when choosing among these event-communication strategies. In this webcast, Scott Meyers covers the pros and cons of void futures as a mechanism for event communication among threads. It's based on information in chapter 7 ("The Concurrency API") of his best-selling new book, Effective Modern C++."--Resource description page. | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a C++ (Computer program language) | |
| 650 | 0 | |a Object-oriented programming languages. | |
| 650 | 6 | |a C++ (Langage de programmation) | |
| 650 | 6 | |a Langages orientés objet (Informatique) | |
| 650 | 7 | |a C++ (Computer program language) |2 fast |0 (OCoLC)fst00843286 | |
| 650 | 7 | |a Object-oriented programming languages. |2 fast |0 (OCoLC)fst01741387 | |
| 856 | 4 | 0 | |u https://learning.oreilly.com/videos/~/9781491934562/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 994 | |a 92 |b IZTAP | ||