>>$CC, $BB, $AA, $11 -- iValue (aligned at 4-bytes boundary) >>0, 0, -- null flag for iValue (aligned at 2-bytes boundary) >>$DD, $33 -- sValue (aligned at 2-bytes boundary) >>0, 0, -- null flag for sValue (aligned at 2-bytes boundary) >>0, 0, -- padding to align iValue2 properly <= i understand why here we >>need >>padding but >>$DD, $CC, $BB, $22, -- iValue2 (aligned at 4-bytes boundary) >>0, 0, -- null flag for iValue2 (aligned at 2-bytes boundary) >>0, 0, -- padding to align iValue3 properly <== why here we need padding? - >>align to what? >>$DD, $CC, $BB, $22, -- iValue3 (aligned at 4-bytes boundary)
Ach sorry - for int it should by divisible by 4 ;-) Ok - now my memory refresh self ;-) regards, Karol Bieniaszewski ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
