str[n]dupa() are available on every modern compiler platform, incl. Clang, ICC, &c. By shortening the third paragraph, it now reads strdupa() and strndupa() are similar, but use alloca(3) to allocate the buffer. pointing squarely to alloca(3), which is scary enough, so drop the extraneous warning, too ‒ this clearly points to "see alloca(3) for the limitations of that allocator". Plus, it's not like malloc(3) doesn't have its problems, too, but I don't see those being touted in the first paragraph; reducing these to the bare minimum, strdup() copies into malloc(3) and you can free it with free(3), strndup() likewise, but up to n, and str[n]dupa() use alloca(3) instead ‒ be wary of what alloca(3) does! doesn't really make sense ‒ it's obvious that, ex definitione, alloca(3) suffers from alloca(3) problems and input limits, just like malloc(3) from the malloc(3) suite's. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>