I wander, why cx member called lx in Windows.inc?
In all reference and h files I have it is cx
In all reference and h files I have it is cx
Maybe to avoid confusion with the register
Exactly. If you rename it 'back' to cx, MASM throws fits cause cx is a reserved keyword for the register.
Silly, but it does that.
Silly, but it does that.
:)
Thanks
Thanks
Somebody ought to hack up ml.exe to allow reserved keywords
as part of structures... :)
as part of structures... :)
kinda funny you run into this now The Svin. yesterday i ran into the undeclared SIZE structure and couldnt figure out why i was getting assembly errors when i manually declared it into my code.
SIZE STRUCT
cx LONG ?
cy LONG ?
SIZE ENDS
to avoid the cx register and the masm SIZE keyword problem hutch or iczelion took the liberty to declare an alternate structure to use.
SIZEL STRUCT
x DWORD ?
y DWORD ?
SIZEL ENDS
anyways i got a good learning experience from this. i now recognize that it really doesnt matter what structure you use as long as it does the same thing.
SIZE STRUCT
cx LONG ?
cy LONG ?
SIZE ENDS
to avoid the cx register and the masm SIZE keyword problem hutch or iczelion took the liberty to declare an alternate structure to use.
SIZEL STRUCT
x DWORD ?
y DWORD ?
SIZEL ENDS
anyways i got a good learning experience from this. i now recognize that it really doesnt matter what structure you use as long as it does the same thing.
Well, I guess it just shows you that SIZE doesn't matter... It's just how you use it...
Ok ruined enough perfectly good threads now... :(
Ok ruined enough perfectly good threads now... :(
keep telling yourself that silver!:grin: anyways i personally beleive all this confusion lies with the entrance diamater. if somene is used to qwords and you give them a byte that can lead to some serious run time errors. statisticly speaking though bytes are most commonly used.
lol Bit <-- Rake
lol Bit <-- Rake
lol bit <-- Rake
Posted on 2002-05-08 00:37:02 by NaN