Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2019-12-19 | Zero node padding before passing to reader sinks | David Robillard | 1 | -0/+1 | |
2019-12-19 | Simplify stack management by popping in bulk at higher levels | David Robillard | 1 | -22/+11 | |
Since all memory used by the reader is POD in the stack, there is no benefit to forcing code to explicitly pop everything pushed to the stack, since any function can record an offset and pop back down to it regardless of what its callers pushed if it knows that it does not need those items. | |||||
2019-12-19 | Use a fixed-size reader stack | David Robillard | 1 | -4/+7 | |
This improves performance, and makes the reader more suitable for embedded or network-facing applications, at the cost of requiring the user to specify a maximum stack size. | |||||
2019-12-19 | Clean up includes and improve source file separation | David Robillard | 1 | -2/+2 | |
2019-12-19 | Clean up and separate internal headers | David Robillard | 1 | -0/+113 | |