.h: header file, its a source file containing declarations (as opposed to .cpp, .cxx, etc. containing implementations), .lib: static library may contain code or just links to a dynamic library. Either way it’s compiled code that you link with your program. The static library is included in your .exe at link time. .dll: dynamic library. … Read more
Converting C source code files to an executable program is normally done in two steps: compiling and linking. First, the compiler converts the source code to object files (*.o). Then, the linker takes these object files, together with statically-linked libraries and creates an executable program. In the first step, the compiler takes a compilation unit, … Read more
DISCLAIMER: My day job is working for a company that develops static analysis tools. I would be surprised if most (if not all) static analysis tools did not have some form of header usage check. You could use this wikipedia page to get a list of available tools and then email the companies to ask … Read more
You should install the development support files for zlib, try: sudo apt-get install libz-dev Other package names: zlib1g-dev. If you’ve already zlib library, make sure you’re compiling your code sources with -lz. See: missing zlib.h in ubuntu.
gcc -H … will print the full path of every include file as a side-effect of regular compilation. Use -fsyntax-only in addition to get it not to create any output (it will still tell you if your program has errors). Example (Linux, gcc-4.7): $ cat > test.c #include <stdbool.h> #include <stdio.h> ^D $ gcc -H … Read more
Backwards Compatibility – Header files are not eliminated because it would break Backwards Compatibility.
It is also possible to set the Product Module Name setting in Build Settings to be the same across your modules (I set it to $(PROJECT_NAME)), so that the <project>-Swift.h file that is generated has the same name across all modules. This eliminates the need for adding/checking preprocessor macros.
FIRST QUESTION: Why aren’t include guards protecting my header files from mutual, recursive inclusion? They are. What they are not helping with is dependencies between the definitions of data structures in mutually-including headers. To see what this means, let’s start with a basic scenario and see why include guards do help with mutual inclusions. Suppose … Read more
It’s common to put an additional @interface that defines a category containing private methods: Person.h: @interface Person { NSString *_name; } @property(readwrite, copy) NSString *name; -(NSString*)makeSmallTalkWith:(Person*)person; @end Person.m: @interface Person () //Not specifying a name for the category makes compiler checks that these methods are implemented. -(void)startThinkOfWhatToHaveForDinner; @end @implementation Person @synthesize name = _name; -(NSString*)makeSmallTalkWith:(Person*)person … Read more
Since this answer still gets voted up, I want to point out that you should almost never need to look in the header files. If you want to write reliable code, you’re much better served by looking in the standard. So, the answer to “where can I find the complete definition of off_t” is “in … Read more