Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unused routines still result in huge .EXE
#1
I was looking this weekend on how to better manage my libraries.  One thought was to include most of my common routines in a single large file and simply load that.  What I found was that this caused the .EXE file size to grow considerably.  I created a .BAS file that did nothing but a print statement and included this large library, of which zero routines were actually used.  The file size was huge compared to using a very small library, of which zero routines were used.

Is there a switch or setting that I can use that will cause unused SUBs and Functions to be excluded at compile time if they are not used?
Reply


Messages In This Thread
Unused routines still result in huge .EXE - by dano - 07-22-2024, 02:46 AM



Users browsing this thread: 4 Guest(s)