pragma

In Visual C++, one may link to a library in the code itself by doing #pragma comment (lib, "libname.lib") . Is something similar possible in g++? The Boost Config library has some support for autolinking, using the relevant compiler-specific code for the particular compiler. However, the docs note that the GCC toolchain doesn't support autolinking : Auto-Linking Most Windows compilers and linkers have so-called “auto-linking support,” which eliminates the second challenge. Special code in Boost header files detects your compiler options and uses that information to encode the name of the

What does the HTTP header Pragma: Public mean? According to the standard , Pragma is implementation dependent (section 14.32), except for no-cache because of its wide use. Cache-Control (section 14.9) is the proper way to control caching. This is what the standard says for a Cache-Control: public : Indicates that the response MAY be cached by any cache, even if it would normally be non-cacheable or cacheable only within a non- shared cache. Useful when you come across this error: http://trac.edgewall.org/ticket/1020 . IE 8 & less seems to like to cache things when they are on a SSL server.

My background is C# but I have to maintain some legacy (MS) C++. In that codebase I stumpled across: #pragma comment(lib, "OtherLib700.lib") where 700 is some versioning. Besides the lib is a DLL with the same name. I first thought that the program would be dependant upon the DLL but after removing it from the system the program still works. There exists a newer version of the DLL, though, which is named OtherLib900... It seems as though the program 'included' the code of the lib so that it's no longer dependant upon the external DLL. (Or that the program 'automatically' uses the newer DLL...)

In my c++ project, there are several #pragma omp parallel for private(i) statements. When I try to track down bugs in my code using valgrind, the OpenMP adornments result in "possibly lost" memory leak messages. I would like to totally disable all of the aforementioned #pragma statements so that I can isolate the problem. However, I use omp_get_wtime() in my code, and I do not wish to disable these function calls. So I don't want to totally disable all OpenMP functionality in my project. How can I simply turn off all the #pragma omp parallel for private(i) statements? I use Eclipse CDT to

Is there something like the ANSI C operator _Pragma in Visual C++? For example, I'm trying to define the following macro: #ifdef _OPENMP #define PRAGMA_IF_OPENMP(x) _Pragma (#x) #else // #ifdef _OPENMP #define PRAGMA_IF_OPENMP(x) #endif // #ifdef _OPENMP So I can circumvent compiler warnings for unknown #pragma omp ... in older GCC compilers. Is there a similar means available in VisualC++? Yes, but it's two underscores: __pragma I'm not sure about how the omp pragma works, however, here's an example using VC++'s optimize pragma: #define PRAGMA_OPTIMIZE_OFF __pragma(optimize("", off)) // These

What exactly will happen to the data segment and text segment if I use the below two lines in my c source code file? #pragma CODE_SECTION(func1, "Sec1") #pragma DATA_SECTION(globalvar1, "Sec2") Source (contains examples): http://hi.baidu.com/jevidyang/blog/item/6d4dc436d87e3a300b55a918.html Note: #pragma is compiler specific, so syntax may vary for your compiler. The DATA_SECTION pragma allocates space for the symbol in a section called section name. The syntax for the pragma in C could be: #pragma DATA_SECTION (symbol, "section name"); The syntax for the pragma in C++ could be: #pragma DATA

I have a chunk of code that crashes unless I build with optimizations off. I'm building with LLVM compiler 2.0 I would like to turn off optimizations by wrapping the offending code with a #pragma compiler directive; or turn off optimizations for an entire file. I've been digging in the clang manual and code; but nothing jumps out at me. Does anyone know how to change the optimizations for a single CU (as opposed to for the entire app)? Brad Larson You can set per-file compiler flags in Xcode. In Xcode 4 (which I assume you're using because of the LLVM 2.0 reference), first select the project