On Sat, 1 Aug 2026, Alejandro Colomar wrote: > From: Collin Funk <[email protected]> >> Joseph Myers <[email protected]> writes: >> >> > I'd rather we add a mandatory deprecation warning to memory.h in glibc. >> >> I would be for this change, and am surprised it has not already been >> done, to honest. The use of memory.h is a good indicator code hasn't >> been touched since the 80s.
I agree. <memory.h> is a legacy header, and it has only redirected to <string.h> for ages, for even-older-code compatibility. Many environments do not have it at all, and let’s leave it at that. It’s so obscure I haven’t needed to use it on *any* of the platforms mksh got ported to, and those are extensive. >Or that it has been touched in 2026. :) Please don’t try to unilaterally introduce even more splintering of portable C programming. This will hurt and make standards into competing instead of compatible again. Thanks. (Please do not add me to the Cc list, I don’t have enough tuits for this.) bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
