C11 standard adds the _Static_assert keyword. This is implemented since gcc-4.6: _Static_assert (0, “assert1”); /* { dg-error “static assertion failed: \”assert1\”” } */ The first slot needs to be an integral constant expression. The second slot is a constant string literal which can be long (_Static_assert(0, L”assertion of doom!”)). I should note that this is … Read more
Compile-time dependency: You need the dependency in your CLASSPATH to compile your artifact. They are produced because you have some kind of “reference” to the dependency hardcoded in your code, such as calling new for some class, extending or implementing something (either directly or indirectly), or a method call using the direct reference.method() notation. Run-time … Read more
A compile-time dependency is generally required at runtime. In maven, a compile scoped dependency will be added to the classpath on runtime (e.g. in wars they will be copied to WEB-INF/lib). It is not, however, strictly required; for instance, we may compile against a certain API, making it a compile-time dependency, but then at runtime … Read more
The difference between compile time and run time is an example of what pointy-headed theorists call the phase distinction. It is one of the hardest concepts to learn, especially for people without much background in programming languages. To approach this problem, I find it helpful to ask What invariants does the program satisfy? What can … Read more