Eric Blake wrote:
Can we use ssize_t instead of size_t for obstack_blank_fast?
Not portably, no. ssize_t need not be the same width as size_t.As I understand it, ssize_t was partly invented to support platforms where 'read' took a 64-bit size_t argument and returned a 32-bit signed result -- and ssize_t is therefore best avoided except when dealing directly with system calls that return ssize_t.