Use a fixed-size reader stack

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.

1 files changed, 8 insertions, 4 deletions

diff --git a/src/stack.h b/src/stack.h
index bcf1434b..c2335b3a 100644
--- a/src/stack.h
+++ b/src/stack.h
@@ -66,9 +66,9 @@ serd_stack_push(SerdStack* stack, size_t n_bytes)
 {
   const size_t new_size = stack->size + n_bytes;
   if (stack->buf_size < new_size) {
-    stack->buf_size += (stack->buf_size >> 1); // *= 1.5
-    stack->buf = (char*)realloc(stack->buf, stack->buf_size);
+    return NULL;
   }
+
   char* const ret = (stack->buf + stack->size);
   stack->size     = new_size;
   return ret;
@@ -85,12 +85,16 @@ static inline void*
 serd_stack_push_aligned(SerdStack* stack, size_t n_bytes, size_t align)
 {
   // Push one byte to ensure space for a pad count
-  serd_stack_push(stack, 1);
+  if (!serd_stack_push(stack, 1)) {
+    return NULL;
+  }
 
   // Push padding if necessary
   const size_t pad = align - stack->size % align;
   if (pad > 0) {
-    serd_stack_push(stack, pad);
+    if (!serd_stack_push(stack, pad)) {
+      return NULL;
+    }
   }
 
   // Set top of stack to pad count so we can properly pop later