diff options
| author | Cœur <coeur@gmx.fr> | 2022-04-25 19:27:18 +0800 |
|---|---|---|
| committer | Leo Izen <leo.izen@gmail.com> | 2022-04-25 09:07:18 -0400 |
| commit | bb5b4b1ba61b67da40c85c34376aced9383fc366 (patch) | |
| tree | b917b0ad45f31c1187c47424de4159cc28aa730f /DOCS/tech-overview.txt | |
| parent | 6407095871b8f177996a6ec3ee9a8c4f06bd63ee (diff) | |
| download | mpv-bb5b4b1ba61b67da40c85c34376aced9383fc366.tar.bz2 mpv-bb5b4b1ba61b67da40c85c34376aced9383fc366.tar.xz | |
various: fix typos
Diffstat (limited to 'DOCS/tech-overview.txt')
| -rw-r--r-- | DOCS/tech-overview.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/DOCS/tech-overview.txt b/DOCS/tech-overview.txt index 4bb06ff764..dd21322bbb 100644 --- a/DOCS/tech-overview.txt +++ b/DOCS/tech-overview.txt @@ -377,7 +377,7 @@ without causing conflicts with other library users in the same process. To any piece of code, a "safe" library's API can simply be used, without having to worry about other API users that may be around somewhere. -Libraries are often not library safe, because they they use global mutable state +Libraries are often not library safe, because they use global mutable state or other "global" resources. Typical examples include use of signals, simple global variables (like hsearch() in libc), or internal caches not protected by locks. @@ -481,7 +481,7 @@ VOs, AOs, demuxers, and more. The frontend usually calls "down" the usage hierarchy: mpctx almost on top, then things like vo/ao, and utility code on the very bottom. -"Callback hell" is when when components call both up and down the hierarchy, +"Callback hell" is when components call both up and down the hierarchy, which for example leads to accidentally recursion, reentrancy problems, or locking nightmares. This is avoided by (mostly) calling only down the hierarchy. Basically the call graph forms a DAG. The other direction is handled by event |