Author Topic: SLL granularity  (Read 3968 times)

0 Members and 1 Guest are viewing this topic.

Offline Patrice Terrier

  • ROMs
  • Hero Member
  • *****
  • Posts: 936
  • User-Rate: +62/-1
    • www.zapsolution.com
SLL granularity
« on: March 11, 2011, 08:41:24 AM »
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.

...
« Last Edit: March 11, 2011, 09:40:02 AM by Patrice Terrier »
Patrice Terrier
GDImage (advanced graphic addon)
http://www.zapsolution.com

Offline Brice Manuel

  • Full Member
  • ***
  • Posts: 154
  • User-Rate: +0/-0
Re: SLL granularity
« Reply #1 on: March 11, 2011, 09:08:04 AM »
I agree 100%.  This is something I will definitely be using in-house.

Offline Jim Dunn

  • Newbie
  • *
  • Posts: 36
  • User-Rate: +4/-0
Re: SLL granularity
« Reply #2 on: March 27, 2011, 09:00:31 PM »
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?

Offline José Roca

  • Administrator
  • Hero Member
  • *****
  • Posts: 2481
  • User-Rate: +204/-0
Re: SLL granularity
« Reply #3 on: March 27, 2011, 10:45:47 PM »
Yes, you have got it right.