4 ms·
> _Py_NewReference() Actually just the name is undefined behavior per C and C++. The standards reserve all identifiers starting with underscore and followed b
by RcouF1uZ4gsC 5y ago
> _Py_NewReference()
Actually just the name is undefined behavior per C and C++. The standards reserve all identifiers starting with underscore and followed by a capital letter to the implementation.
- zabzonk 5y agoQuite right. I have never understood this obsession that people have with underscores. Here's something I wrote about them some time ago: https://punchlet.wordpress.com/2009/12/01/letter-the-second/ https://punchlet.wordpress.com/2009/12/01/letter-the-second/
- mayli 5y agoAgreed, the obsession pretty much true, but without really practical reason behind it.
- kevin_thibedeau 5y agoThey make up for C's lack of namespaces. If you're not writing a compiler or OS you shouldn't be profligate with them.
- david2ndaccount 5y agoThat being UB is more of trivia than anything else. It’s UB because it allows freedom for compilers and standard library implementations to change their implementation without it being a “breaking” change, not because the compiler will produce nasal demons if you commit the crime of naming anything _Py_NewReference.