[<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
  SECTION INTO
------------------------------------------------------------------------------

  Purpose : Specify files to be placed in an external overlay

  Syntax  : SECTION INTO <ovlname> [FILE [d:][path]<filename>[,
            [d:][path]<filename>...] ]

  Default : Disabled

  Example : SECTION INTO TESTOVL FILE C:\OBJ\OUT1

  The SECTION INTO command is used to specify the name of an external
  overlay file for the overlays. The file may have any extension except
  .EXE, and if no extension is specified then .OVL is assumed. The first
  SECTION INTO command must precede the first overlaid FILE command,
  otherwise an internal overlay within the OUTPUT file will be created and
  all SECTION INTO commands will be ignored.

  Once an overlay file has been specified using the SECTION INTO command,
  all overlaid code will be placed in the same file until a SECTION INTO
  command with a different file name is found. At this time a new overlay
  file will be created.  Output may be spread between the overlay files by
  the use of multiple SECTION INTO commands.

  Once an internal overlay has been created, all SECTION INTOs will be
  ignored and all overlaid procedures will be stored internally. Once an
  external overlay has been created it is not possible to create an
  internal overlay. Blinker has a limit of 15 external overlays in this
  version.

  At program runtime, one file handle is allocated to each overlay file,
  so it may be necessary to increase the number of file handles available
  to the program.

See Also: BEGINAREA ENDAREA
This page created by ng2html v1.05, the Norton guide to HTML conversion utility. Written by Dave Pearson