mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-10-06 16:09:43 +00:00
Minor typo fixes
This commit is contained in:
parent
c974318686
commit
a9c247bdab
|
@ -1,13 +1,13 @@
|
|||
# POD
|
||||
|
||||
POD (plan old data) is a sort of data container. It is comparable to
|
||||
POD (plain old data) is a sort of data container. It is comparable to
|
||||
DBus Variant or LV2 Atom.
|
||||
|
||||
A POD can express nested structures of Objects (with properties), Vectors,
|
||||
Arrays, sequences and various primitives types. All information in the POD
|
||||
is laid out sequentially in memory and can be written directly to
|
||||
storage or exchanged between processes or threads without additional
|
||||
marshalling..
|
||||
marshalling.
|
||||
|
||||
Each POD is made of a 32 bits size followed by a 32 bits type field,
|
||||
followed by the pod contents. This makes it possible to skip over unknown
|
||||
|
@ -86,7 +86,7 @@ spa_pod_builder_int(&b, 5);
|
|||
spa_pod_builder_float(&b, 3.1415f);
|
||||
```
|
||||
|
||||
The we close the container by popping the frame again:
|
||||
Then we close the container by popping the frame again:
|
||||
|
||||
```c
|
||||
struct spa_pod *pod;
|
||||
|
|
|
@ -83,7 +83,7 @@ ships with 2 types of mainloop implementations. We will use the
|
|||
`struct pw_main_loop` implementation, we will see later how we can
|
||||
use the `struct pw_thread_loop` implementation as well.
|
||||
|
||||
The mainloop is an abstraction of a big poll loop, wiating for events
|
||||
The mainloop is an abstraction of a big poll loop, waiting for events
|
||||
to occur and things to do. Most of the PipeWire work will actually
|
||||
be performed in the context of this loop and so we need to make one
|
||||
first.
|
||||
|
|
Loading…
Reference in a new issue