I wander, why cx member called lx in Windows.inc?
In all reference and h files I have it is cx
Posted on 2002-05-04 13:30:45 by The Svin
Maybe to avoid confusion with the register
Posted on 2002-05-04 13:42:55 by Kudos
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.
Posted on 2002-05-04 19:20:14 by Ernie
:)
Thanks
Posted on 2002-05-04 20:04:56 by The Svin
Somebody ought to hack up ml.exe to allow reserved keywords
as part of structures... :)
Posted on 2002-05-05 06:44:12 by f0dder
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.
Posted on 2002-05-07 21:52:43 by smurf
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... :(
Posted on 2002-05-07 21:55:05 by Sliver
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
Posted on 2002-05-07 22:18:18 by smurf

lol bit <-- Rake
Yes! That is one of the reasons I chose this handle.
Posted on 2002-05-07 22:28:11 by bitRAKE
Posted on 2002-05-08 00:37:02 by NaN