Re: valgrind leak I can't find

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:
 

This is the type's struct:
 
typedef struct {
     int _size;
     int _cap;
     char** _values;
} VecStr;

 
What's with the leading underscores for member names?
 
It means ending with ->_ later on, which seems pointless extra
clutter.

 
 
C++ is responsible for this.
 
C++ made the usage of 'this->' optional when calling member
functions.
 
As a result, when C++ programmers encounter 'i' in the middle of a
function, they might not know where it comes from.
 
If 'this->' were not optional, 'this->i' would clarify that.
 
To avoid confusion, many C++ programmers use prefixes like 'm_' that
can't be ignored.
 
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 “internal use” indicator.
    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