Tweet
TIP: Using CopyRect instead of LSET saves me almost 1K
(If you need to copy a RECT of course)
(If you need to copy a RECT of course)
-
-
How did you measure that? Remember that the EXE size bears little resemblence to the real memory image... you need to use the compile stats to determine the exact "saving".
In my simple test to verify your claim using the following code:
#COMPILE EXE
#INCLUDE "win32api.inc"
FUNCTION PBMAIN
DIM a AS rect
DIM b AS rect
' a = b ' unrem one or the other...
' CopyRect a,b
END FUNCTION
I get the following code results:
Note that LSET is not required when copying a UDT structure... LSET A=B is the same as A=B, but using LSET adds slightly more code to the application.Code:[i]Neither a=b CopyRect[/i] 592 bytes code 624 code 608 code 1103 RTL 1609 RTL 1103 RTL 688 bytes dgroup 688 dgroup 688 dgroup 1791 bytes memory image 2297 memory image 1791 memory image
Therefore, the apparent memory saving is 2297-1791 = 506 bytes. If we add the LSET keyword into the A=B line, then the code jumps to 2499-1791=708 bytes.
Interesting!
-------------
Lance
PowerBASIC Support
( mailto:[email protected][email protected]</A> )
Lance
mailto:[email protected] -
I was common to use LSET in VB.
I know PB can use LSET to copy strings to UDT's etc..
It's just a tip, useless, many apps won't notice the ~1k added if there 100k or so.
Just very small apps may gain a bit.
And (not tested), LSET will only add 1k even if you use it a lot in your app i guess.
Bye,
Comment
Comment