I think I see what Luis means: The program, with the a := 9 occupies eight bytes, per Brad's dump above. That's two longs. Without the assignment, the program occupies five bytes. But that's still two longs, since you have to count whole longs.
Phil Pilgrim (PhiPi) said...
I think I see what Luis means: The program, with the a := 9 occupies eight bytes, per Brad's dump above. That's two longs. Without the assignment, the program occupies five bytes. But that's still two longs, since you have to count whole longs.
-Phil
That makes sense.
With second example (screens) should be something seemed.
Many thanks boys!
Post Edited (Luis Digital) : 3/25/2009 9:32:29 PM GMT
Yes indeed. Phil is absolutely right, as the variables and stack are located after any object code, and they both must be long aligned there is padding inserted to bring the code length up to a long boundary if required.
I'll have a look at the dialog box cutting bits off. I've not played with the alignment of components much outside of my laptop and development box. They both have the same DPI setting and at least 1024x768 resolution. I'll see if I can reproduce that mis-alignment and get it fixed
Thanks for the screenshot. They help a lot.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Look these screens.
Post Edited (Luis Digital) : 3/25/2009 12:01:19 AM GMT
-Phil
That makes sense.
With second example (screens) should be something seemed.
Many thanks boys!
Post Edited (Luis Digital) : 3/25/2009 9:32:29 PM GMT
I'll have a look at the dialog box cutting bits off. I've not played with the alignment of components much outside of my laptop and development box. They both have the same DPI setting and at least 1024x768 resolution. I'll see if I can reproduce that mis-alignment and get it fixed
Thanks for the screenshot. They help a lot.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.