Thread: #pragma directive

I am trying to understand #pragma directive in language.

https://www.geeksforgeeks.org/pragma-directive-in-c-c/

I don't understand what can be it's benefits

Code:

#include<stdio.h>          
int show(int x)
{     
    x = 5;
    printf("x = %d", x);
 
}
            
int main()
{
    show(10);
      
    return 0;
}

Even after using C for 26 years (and professionally for about half of that time), I have not once had a need for the #pragma directive. That's even in a codebase of nearly 100k lines that I develop/maintain.

That's a little surprising I always enable compiler warnings at a high level (if not the highest), check all warnings I get, and disable those that are only informal or those that I won't fix using pragma directives, after double checking. Of course this takes some additional time. And it may require branching for the preprocessors of different compilers. I'm only a programming hobbyist though (for ~15 years now).

aGerman: If there's any type of warning that I don't care about, I'll generally want to ignore all warnings of that type, so I can just add a -Wno-foo option when building. But usually I'll try to fix what's causing the warning instead. (E.g., for unused variable warnings, I'll either add -Wno-unused-variable to the build options or just remove the unused variables.)

I agree as long as you have full control to the compilation. As soon as you publish code you do neither know the compiler nor the settings that people prefer. At some point I began using several commonly used compilers like GCC, Clang, and MSVC. I also often push/pop the suppression of certain warnings for the whole file.