| Deutsch English Français Italiano |
|
<pan$8db48$12dfbf80$ce60889d$2a8f67fc@invalid.invalid> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!bluemanedhawk.eternal-september.org!.POSTED!not-for-mail From: Blue-Maned_Hawk <bluemanedhawk@invalid.invalid> Newsgroups: comp.lang.c Subject: Re: valgrind leak I can't find Date: Sat, 24 Aug 2024 11:47:02 -0000 (UTC) Organization: A noiseless patient Spider Lines: 42 Message-ID: <pan$8db48$12dfbf80$ce60889d$2a8f67fc@invalid.invalid> References: <j8idnQlHTPZXZFv7nZ2dnZfqn_GdnZ2d@brightview.co.uk> <va75pv$djqu$1@dont-email.me> <va76q6$dljb$2@dont-email.me> <1c5db75fd1fd3b0e61bd2517a38f2829d0aeee6c.camel@tilde.green> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 24 Aug 2024 13:47:03 +0200 (CEST) Injection-Info: bluemanedhawk.eternal-september.org; posting-host="0db1dfb28db18019f54f64fbffecc8a6"; logging-data="1459036"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/EGUTyQKZBC1ZqrBa1zls8PGaSM+sssUY=" User-Agent: Pan/0.154 (Izium; 517acf4) Cancel-Lock: sha1:SMqjJjfLBikevckxZbrPV9jPjys= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAIAAADYYG7QAAACh0lEQVRYw71Z21bD MAzzevbfkr4cHjrSXJyL044+MDa6WLEl2SkvkrZ1AbAvXO+bUGSCPYnsuIVGMpm ZLnjX718GhAKNsp8lON2F9VrhELwIgJlBepkZjA78rVK+FkmNhEJK76UsJlz8+E rJsjrpYouhLo/SC6qPHgakFOR8wV9+8rCfO/I/oVnmUZUp42/LW2XkLj9TCFNM9 jp5g2EmHZgpYZjCOkYU7sXVogRylJqpdggoFLG1g09Flah/7kErCxzR9HgXPYsq 0glb9cxjIz2Vsk9AmAoCSxECpD713joMKjQqLAtmMqJmXjdVvlMnMQCVITotJd1 z+fh1f1NNo+vuc1KnhWUmY7t03vydTud9BbXCtN3L2PL3bK7JCNG0GHzuZxafyB fxevCxpm1vrwZltqw6SILCcdoCE6PGQC8wZWDA9Or7Qp5s3lAZezys0nDazs9S9 R0TjwEiksRxLkNPC1NMMWPs1bj0Ei0Yuo+JVtFLuzP1NRJ16qXWN8DhhtmS4PDg O6mqRxs4bEJrYt087mSIow/1VzW2oFlMQuiuIy/KsUagvhdw6hSjJGlIavbLF8x j3X47bccLcUSi0dkWh1nUZNhANT1tHKUXrNxNLbd9KPb9wDDVrKwmPQMOPQ1oy6 k5I1DwzDeRJd3jVIhDAUxq3ngzJG4CCkNXZxZVMcjefoK2J0gUY2S3rxz/RuTFx 2zHd9U+obimJXMG4edsk/2j5pTU5G1MmzbRLxkfq5EiT1GGsidvMGzi+1goGb2l GCrN+nGnV8xj3q3JLRDVPL96vUc7Z4aJ3TN1mVqWAMJMfG+Jxh6TQqP+92iZkCU xtglds1AB6r0aiSHKcnFck+p/c/0CbacFLQcajGcAAAAASUVORK5CYII= X-Face: Taumatawhakatangihangakoauauotamateaturipukakapikimaungahoronuku pokaiwhenuakitanatahu Bytes: 3896 Annada Behera wrote: > On Thu, 2024-08-22 at 08:18 -0300, Thiago Adams wrote: > > <snip/> > >> 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 That's an entirely different convention that is much more common cross- linguistically. I've seen a good bit of C code that's used that for various parts of interfaces that need to be given separate names, but aren't meant to be used directly, such as identifiers constructed in the expansion of a macro. I've personally taken to the habit of naming macros used exclusively to get other macros to work with the name of the macro they're making work prefixed by a number prefixed with an underscore. -- Blue-Maned_Hawk│shortens to Hawk│/blu.mɛin.dʰak/│he/him/his/himself/Mr. blue-maned_hawk.srht.site Made with inadequate loophole sealant!