Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!news.quux.org!tilde.green!.POSTED.103.160.128.7!not-for-mail
From: Annada Behera <segfault@tilde.green>
Newsgroups: comp.lang.c
Subject: Re: valgrind leak I can't find
Date: Thu, 22 Aug 2024 17:31:42 +0530
Organization: tilde.green
Sender: segfault@tilde.green
Message-ID: <1c5db75fd1fd3b0e61bd2517a38f2829d0aeee6c.camel@tilde.green>
References: <j8idnQlHTPZXZFv7nZ2dnZfqn_GdnZ2d@brightview.co.uk>
	 <va75pv$djqu$1@dont-email.me> <va76q6$dljb$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Injection-Info: tilde.green; posting-account="segfault@tilde.green"; posting-host="103.160.128.7";
	logging-data="2847621"; mail-complaints-to="admins@tilde.green"
User-Agent: Evolution 3.52.2
In-Reply-To: <va76q6$dljb$2@dont-email.me>
Bytes: 2352
Lines: 43

On Thu, 2024-08-22 at 08:18 -0300, Thiago Adams wrote:
> On 22/08/2024 08:01, Bart wrote:
> > On 22/08/2024 09:41, Mark Summerfield wrote:
> >=20
> > > This is the type's struct:
> > >=20
> > > typedef struct {
> > > =C2=A0=C2=A0=C2=A0=C2=A0 int _size;
> > > =C2=A0=C2=A0=C2=A0=C2=A0 int _cap;
> > > =C2=A0=C2=A0=C2=A0=C2=A0 char** _values;
> > > } VecStr;
> >=20
> > What's with the leading underscores for member names?
> >=20
> > It means ending with ->_ later on, which seems pointless extra
> > clutter.
>=20
>=20
> C++ is responsible for this.
>=20
> C++ made the usage of 'this->' optional when calling member
> functions.
>=20
> As a result, when C++ programmers encounter 'i' in the middle of a=20
> function, they might not know where it comes from.
>=20
> If 'this->' were not optional, 'this->i' would clarify that.
>=20
> To avoid confusion, many C++ programmers use prefixes like 'm_' that=20
> can't be ignored.
>=20
> Since many C programmers also work in C++, this pattern can sometimes
> influence C code as well.

Although I think this is stupid thing to do when writing C, the same
convention also exits in Python PEP-8 [1]

    _single_leading_underscore: weak =E2=80=9Cinternal use=E2=80=9D indicat=
or.
    E.g. from M import * does not import objects whose names start with
    an underscore.

[1]: https://peps.python.org/pep-0008/#descriptive-naming-styles