Yes that section raised my hackles too, to the point where I'm suspicious of the whole article.

The solution, in my opinion, is to either document that strclone()'s return should be free()'d, or alternately add a strfree() declaration to the header (which might just be `#define strfree(x) free(x)`).

Adding a `char **out` arg does not, in my opinion, document that the pointer should be free()'d.