Re: alx-0096r1 - string (and nonstring) copying

Alejandro Colomar <[email protected]> Tue, 28 Jul 2026 17:58:48 +0200

Newsgroups	org.kernel.vger.linux-man
Message-ID	<amjRQGFh1PvsjJSC@devuan>

Hi Mark,

On 2026-07-28T17:04:20+0200, Alejandro Colomar wrote:
[...]
> > That is, memtostr(str, mem, n), introducing a whole
> > new area of potential confusion that was not present in any existing
> > mem*() or str*() functions.  If reducing potential confusion is that
> > important I would have expected maybe strfrommem(str, mem, n) or
> > similar.
> 
> Hmmmm, interesting suggestion!  That makes it resemble the strfromd(3)
> family, with which it actually has some (minor) relation.  (It might be
> a bit
> 
> strfrommemcat() would be a weird name, because the cat is next to mem
> instead of str.  Should it be strcatfrommem()?

On the other hand, there's precedent in strtol(3) having the arguments
reversed compared to the name.  Programmers are used to having the
destination in the first parameter.

Anyway, I'll mention these alternative names in the proposal.


Cheers,
Alex

-- 
<https://www.alejandro-colomar.es>

signature.asc (application/pgp-signature, 833 B)