Sujet : Re: valgrind leak I can't find
De : Keith.S.Thompson+u (at) *nospam* gmail.com (Keith Thompson)
Groupes : comp.lang.cDate : 24. Aug 2024, 22:04:33
Autres entêtes
Organisation : None to speak of
Message-ID : <87y14lfx9a.fsf@nosuchdomain.example.com>
References : 1 2 3 4 5 6
User-Agent : Gnus/5.13 (Gnus v5.13)
scott@slp53.sl.home (Scott Lurndal) writes:
Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> writes:
Annada Behera wrote:
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.
>
Such prefixes for structure (class) members date back to the
earliest C compilers, where structure member names were first-class
symbols, unqualified by the structure name (any member name could
be used with any pointer regardless of pointer type). Thus some
means was necessary to disambiguate member names. Remnants of
that still exist in POSIX (e.g. the field names for struct stat
all start with "st_").
And in ISO C, where the members of struct tm have names starting with
"tm_".
-- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.comvoid Void(void) { Void(); } /* The recursive call of the void */
valgrind leak I can't find
Re: valgrind leak I can't find
