If you deploy one executable, ok, but if you want to create a handfull of executables (following unix logic of many small programs) then you have a problem.
EVERY executable will have the same code again again again, i think libraries have been created to address exactly this issue. about the library hell, why we cant use lib versions ? lets say, libpas.so.2.4.4 for fpc 2.4.4 libpas.so.2.6.1 for fpc 2.6.1 libpas.sysutils.so.2.4.4 libpas.classes.so.2.4.4 etc... etc... the only problem i see is the lack of a sane way to export class instances to/from the libraries. 2012/4/29 Florian Klämpfl <flor...@freepascal.org>: > Am 29.04.2012 14:23, schrieb Jorge Aldo G. de F. Junior: >> What would be usefull is to move the loads of code stored in >> sysutils/runtime into a dll/so. >> >> thats what makes C code look "smaller", theres a nice libc (and >> others) there that groups mostly used functions into a single >> instance, while in pascal every executable replicates the very same >> code for each instance. >> >> make sysutils/runtime etc an external loadable library and we are >> going to see FPC generate similar sized executables for similarly >> sized programs. > > It makes them look smaller but their footprint is actually larger so > this is exactly what Ido doesn't want. > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
