- 29 Dec, 2016 5 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
- 28 Dec, 2016 4 commits
-
-
David Reid authored
-
David Reid authored
The rationale for this is that it's to unreliable and inconsistent across each backend and not worth the added maintenance cost.
-
David Reid authored
-
David Reid authored
-
- 22 Nov, 2016 1 commit
-
-
David Reid authored
-
- 14 Nov, 2016 14 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
These changes add a mal_context parameter and moves the output device to the last parameter for consistency with mal_context_init().
-
David Reid authored
-
David Reid authored
-
- 13 Nov, 2016 7 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
- 06 Nov, 2016 2 commits
-
-
David Reid authored
-
David Reid authored
-
- 28 Oct, 2016 2 commits
-
-
David Reid authored
-
David Reid authored
-
- 27 Oct, 2016 1 commit
-
-
David Reid authored
-
- 26 Oct, 2016 4 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
Rationale: 1) It allows the callbacks to be set at initialization time which feels a bit more intuitive to me. 2) It avoids the need to call mal_device_set_send_callback(), etc. 3) It's a bit more consistent with the onLog callback. Previously, onLog would be passed to mal_device_init(), whereas onSend, etc were set with mal_device_set_send_callback(), etc. which feels needlessly inconsistent.
-