It is just a JIT compiler test. A "good" compiler would deduce the intent and eliminate all of the excess excpetion handling and place optimized code inline on the first pass. This eliminates the need for the programmer to think because the compiler has implemented the new DWIM (Do what I mean) facility. Seriously in MVS Assembler it would be XR R0,R0 L R1,VALUE D R0,=A(2) JZ EVEN process odd number J M_010 EVEN DS 0H process even number M_010 DS 0H . . .
Sam
Must be government work!
Sam
As previously mentioned you should not expect an exact comparision when working with floating point numbers. To check equality you need to compare the differnce to epsilon. If the difference is < or = epsilon then the numbers are equal. Otherwise they are not. This is done as follows: take the absolute value of the difference of the absolute values of the two floating point numbers and compare the result to epsilon. If the difference is less than or equal epsilon then the numbers are equal. if( FLT_EPSILON =< fabsf( fabsf(f1) - fabsf(f2) ) ) printf( "numbers are equal\n" ); else printf( "numbers are not equal\n" ); NOTE: there are double precision variants of epsilon and fabsf. Sam Sam
Use a virtual list control. Rather than loading all the rows when the list is created you just load the columns assoicated with the rows that are displayed. You recieve "scrolling" messages, (both up and down), that tell you when additional row data is required. Just look up "virtual list control" in your MSDN documentation. Or check out some of these articles. Code Guru article[^] MSDN Article[^] Other Article[^] Sam
In a word: boundary alignment. ID is an unsigned int and MAJOR, an enum, also defaults to an int datatype. Ints are 4-byte fields that are naturally aligned on four byte boundarys. Therefore the compiler places the int fields on four byte boundarys. Doubles go on an eight byte boundary. If the struct does not have the fields ordered in descend size of datatypes, (doubles, ints, short ints and finally char/char array), then the compiler silently inserts unreachable filler alignment bytes. Doubles, ints, etc. are boundary aligned to improve register load performance. On certain types of machines fetching unaligned data can cause an execption. You can use a #pragma to modify the default boundary alighment. You can see the result of what the compiler has done by generating a listing that details the struct. Offset length Field 0 10 name 10 2 unreachable filler inserted by the compiler 12 4 ID 16 1 sex 17 3 unreachable filler inserted by the compiler 20 4 major Total length=24 Sam
Hello All I'm attempting to build an SDI application with a splitter window. In the right window, I want to add a propertysheet that contains several propertypages. I am able to do this just fine in dialog box; however, I can't figure out how to add a propersheet/page directly to the right hand window of an SDI application. Your help is appreciated. sam