Re: KMime API review

--nextPartI9ZLxtzKSR2qYYZWzI1kZg
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Volker Krause <[email protected]>
To: [email protected]
Subject: Re: KMime API review
Date: Thu, 05 Feb 2026 17:57:28 +0100
Message-ID: <[email protected]>
Organization: KDE
In-Reply-To: <[email protected]>
References: <2013350.PYKUYFuaPT@xps15> <[email protected]>
MIME-Version: 1.0

On Mittwoch, 4. Februar 2026 16:31:26 Mitteleurop=C3=A4ische Normalzeit Sun=
e=20
Vuorela wrote:
> On 2025-09-15, Albert Astals Cid <[email protected]> wrote:
> > As requested during Akademy.
>=20
> I have been toying a bit with the new API, and so far I at least have a
> couple of questions:
>=20
> Content/Message:
>=20
>   template <typename T> T *header(CreatePolicy create =3D Create);
>=20
> Who owns the header if it is just created? This might just be a
> documentation issue
> (and similar for other headers)

https://invent.kde.org/pim/kmime/-/merge_requests/201 clarifies the=20
documentation.

> We both have
> parent/child ownership explicit Content(Content *parent =3D nullptr);
>  and Content in unique_ptr's.

Removing the parent argument from the ctor is already in progress, waiting =
on=20
MRs in messagelib to land which remove the last uses of that.

Regards,
Volker
--nextPartI9ZLxtzKSR2qYYZWzI1kZg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHkEABECADkWIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCaYTL+BsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0kdT0QCfThtBXlkdkhlXBsNOwzEP
CtAcpFsAnRztdFjKxpeO5zj2qcS6y7OWCwMx
=gmnm
-----END PGP SIGNATURE-----

--nextPartI9ZLxtzKSR2qYYZWzI1kZg--