Hacker News new | ask | show | jobs
by repiret 12 days ago
Because then the caller needs to treat it differently from non-empty buffers.
1 comments

No, it doesn't. It calls:

  void buffer_free(void *buf)
  {
     if (buf != null_buffer_singleton)
       free(buf);
  }
...which treats it differently from non-empty buffers :)

But frankly, having a 1-byte buffer, pointer to which can serve as a sentinel value à la NULL (but dereferenceable!), and which you can pass to free() without it being deallocated is indeed rather useful.