Click above to get retro games delivered to your door ever month!

/clpp:<size>            Set pad size for Clipper-specific incremental link
---------------------------------------------------------------------------------

 Syntax:

 Size is the size of the segment pad value for incremental linking in bytes.
 It can range from 0 to 255.

 Description:

 This option directs WarpLink to change the size of the segment pad that
 is added during incremental linking.  The default of 48 bytes is the
 number of bytes that you can safely add to each Clipper procedure after
 the initial full link without causing subsequent incremental links to fail.

 A non-zero pad value will increase the size of the Clipper procedures (in
 overlays or the root) in your program for incremental linking.  The
 larger the pad value, the greater the increase.  Every Clipper procedure
 (segment) is padded with the amount of bytes specified by the /clpp
 option.

 Padding in the root procedures will directly affect both the .EXE file
 size and the memory overhead of your program.  Padding in overlaid
 procedures will only directly affect the overlay file size and not your
 program's memory requirements, except in those rare cases where the
 larger overlay size may cause your overlay pool size requirements to go
 up 1K or 2K, at most.

 The /clpp option is ignored by WarpLink if the /clpi option is not
 specified.  After a program is incrementally linked, the original /clpp
 pad value will be used until the incremental link fails and a full link is
 performed.  Changing the pad value from its original setting will have
 no effect during successful incremental links.

 Users:

 The /clpp option can only be used by Clipper programmers.

----------------------------------[ Example ]------------------------------------

 The following example  links the Clipper DBU program. 

 . overlay pool is set to  56K bytes                      ->  /op:56

 . reload option is used                                  ->  /r

 . incremental linking will be used                       ->  /clpi

 . incremental linking "pad" size will be set to 24bytes  -> /clpp:24)

 All of the .OBJ files will be overlaid except  DBU.OBJ and OVLMGR.OBJ, and
 the Clipper EXTEND.LIB file will also be overlaid. This example will create
 the following three files:

 DBU.EXE, DBU.OVL, and DBU.ILF.

 When any of these .OBJ files are modified and recompiled, and their size
 doesn't change significantly, the  next time this  application is linked
 you will notice a significant time reduction.

  warplink  /op:56 /r /clpi /clpp:24  (dbu+
  dbuview+dbustru+dbuedit+dbuindx+
  dbucopy+dbuutil+dbuhelp)+
  ovlmgr.obj
  ,,,clipper+extend