[fpc-devel] Interfaces vs. smartlink issue
Hello, I noticed that, within a unit, all interface wrappers (groups of 'WRPR_*' symbols) are placed into one assembler unit together with unit initialization/finalization code (sorry, do not know the exact term for assember unit). As a consequence, init/final code pulls in *all* interface wrappers, which in turn pull in every class that implement an interface. That effectively disrupts smartlinking of the unit. Does this happen on purpose? Perhaps each interface wrapper should be placed into its own assembler unit? Sergei ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Interfaces vs. smartlink issue
Hello, I noticed that, within a unit, all interface wrappers (groups of 'WRPR_*' symbols) are placed into one assembler unit together with unit initialization/finalization code (sorry, do not know the exact term for assember unit). As a consequence, init/final code pulls in *all* interface wrappers, which in turn pull in every class that implement an interface. That effectively disrupts smartlinking of the unit. Does this happen on purpose? Perhaps each interface wrapper should be placed into its own assembler unit? It is legacy. You can improve it to put the wrappers for one interface definition in its own section. Peter ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
