For me SLLs, are a handy solution for in-house programming, to build multiples DLL or EXE re-using the same brick of code from a PBLIB (as long as there is no need to use globals).
It is very important to use huge granularity when doing SLLs, because the code is compiled at the time of the SLL creation, and everything being part of the SLL becomes part of the final EXE or DLL.
Note: SLL is not meant as a replacement for standard DLL.
...
I agree 100%. This is something I will definitely be using in-house.
So instead of compiling my huge JIMS-COMMON.INC file into one SLL, I should plan on breaking the JIMS-COMMON.INC down into 1-function-per-SLL, and then add those 115 SLL's into PBLIB.
Then include the 1 JIMS-COMMON.PBLIB into every program, which would only link the specific functions (SLL's) that I need for that executable...
Does that sound right?
Yes, you have got it right.