assertions

问题 How can I enable the assert keyword in Eclipse? public class A { public static void main(String ... args) { System.out.println(1); assert false; System.out.println(2); } } 回答1: To be specific: Go to Run->run configuration select java application in left nav pan. right click and select New . select Arguments tab Add -ea in VM arguments. 回答2: If anyone wants to enable assertions by default (in contrast to enabling them for just a single run configuration), it is possible with the following

问题 Is there a concise, built-in way to do equals assertions on two like-typed arrays in JUnit? By default (at least in JUnit 4) it seems to do an instance compare on the array object itself. EG, doesn\'t work: int[] expectedResult = new int[] { 116800, 116800 }; int[] result = new GraphixMask().sortedAreas(rectangles); assertEquals(expectedResult, result); Of course, I can do it manually with: assertEquals(expectedResult.length, result.length); for (int i = 0; i < expectedResult.length; i++)

问题 I\'d like to implement an \"assert\" that prevents compilation, rather than failing at runtime, in the error case. I currently have one defined like this, which works great, but which increases the size of the binaries. #define MY_COMPILER_ASSERT(EXPRESSION) switch (0) {case 0: case (EXPRESSION):;} Sample code (which fails to compile). #define DEFINE_A 1 #define DEFINE_B 1 MY_COMPILER_ASSERT(DEFINE_A == DEFINE_B); How can I implement this so that it does not generate any code (in order to

问题 I have been reading some source code and in several places I have seen the usage of assert . What does it mean exactly? What is its usage? 回答1: The assert statement exists in almost every programming language. It helps detect problems early in your program, where the cause is clear, rather than later as a side-effect of some other operation. When you do... assert condition ... you're telling the program to test that condition, and immediately trigger an error if the condition is false. In