>>>>Hi,
>>>>
>>>>I wonder if a commented code adds to the size of the .EXE? My guess is that since the commented code increases the size of the .VCT file (of the class library where the code resides) it has to affect the .EXE; that is, it has to increase its size. Does it make sense?
>>>
>>>I believe if you put a compiler directive around the comments they will not be compiled in. #IF .F. comments #ENDIF
>>
>>I understand that. But my question that I should have posed was differently, does the size of the class .VCT file affects the size of the .EXE. That is, even if I comment the code or put it within #IF #ENDIF, the size of the .VCT file will go up (just the way VFP memo grows). And I am not sure if VFP at build time does not pull the .VCT file in the .EXE. Obviously it (VFP) does not pull the code into the .EXE but I am not sure what it does with the .VCT file. I will probably do a test of adding tons of commented code (or #IF #ENFID) and rebuild the .EXE to see if the size of the .EXE will change.
>>Thank you.
>
>I'm pretty sure the exe size does grow. There is the code and there is the psuedo-compiled object code in the VCT. If you need the debug info - depends on how much the app is ready for prime-time - then excluding comment will keep the VCT size smaller. You will have to do pack the project after changes are made to a VCT.

Thanks.