Module size in documentation

[AZJIO]

Is it important to you that the module size is specified in the documentation?
I compiled with the module to know how much the executable file increases.

Linux x64 (ASM):

UseLZMAPacker = 252 kb
UseBriefLZPacker = 35 kb
UseZipPacker = 347 kb
UseTarPacker = 347 kb
RegularExpression = 166 kb
Scintilla = 2.2 Mb
OpenWindow = 72 kb
SysTrayIcon+OpenWindow = 85 kb
CanvasGadget = 143 kb
UseGIFImageDecoder = 35 kb
UseJPEG2000ImageDecoder = 342 kb
UseJPEGImageDecoder = 145 kb
UsePNGImageDecoder = 186 kb
UseTGAImageDecoder = 23 kb
UseTIFFImageDecoder = 634 kb
UseJPEG2000ImageEncoder = 342 kb
UseJPEGImageEncoder = 125 kb
UsePNGImageEncoder = 195 kb
JSON = 35 kb
Map = 27 kb
XML = 220 kb

1. Sometimes it's easier to write a string parser instead of importing a regular expression engine
2. I use gif instead of png because of the module size when creating compact programs.

[Sergey]

Different versions can be different sizes of modules. Unnecessary work to track changes in the size of each module in three operating systems
Just compile and see how much the size of the created application will change

[Fred]

It's interesting, but keep in mind than some modules share the sames component (for example if you use both UseZipPacker and UseTarPacker size won't change much against only one of those.

[AZJIO]

in three operating systems

*2 (asm/c-backend)
*2 (x32/x64)
You can make an average option or a table for current options. You can make a separate page in the help file. You can do this by users on the forum in this thread. I'm busy right now, but later I will post the sources so that they can be used to easily create files and display their size.