c - Why do names that are not part of the implementation still use the double underscore naming convention? -


aren't double underscores reserved implementation? i'm referring this. people seem ignore convention time.

here's code:

signed int __cdecl upload_exploit() { int device_type; signed int payload_address; int free_address; int deviceerror; char *chunk_headers_ptr; ... 

here convention defined:

in addition names documented in manual, reserved names include external identifiers (global functions , variables) begin underscore (‘_’) , identifiers regardless of use begin either 2 underscores or underscore followed capital letter reserved names. library , header files can define functions, variables, , macros internal purposes without risk of conflict names in user programs.

edit:

although bad example, spirit of question still stands: have seen programmers "incorrectly" use double underscore. connotation carry? trying convey function/keyword?

people write lot of things invalid c. lack of strictness compilers principal reason they're able away it. in case of example linked, not seem code doing wrong. rather illegally defining identifiers in reserved namespace, it's using implementation-defined identifiers provided implementation in standard headers.


Comments

Popular posts from this blog

OpenCV OpenCL: Convert Mat to Bitmap in JNI Layer for Android -

android - org.xmlpull.v1.XmlPullParserException: expected: START_TAG {http://schemas.xmlsoap.org/soap/envelope/}Envelope -

python - How to remove the Xframe Options header in django? -