Chapter Contents |
Previous |
Next |
Prelinking C and C++ Programs |
Prior to Release
6.50, a problem frequently encountered was an attempt to process an object
deck with
cool
that had already been prelinked by
cool
.
This caused a number of problems, not obviously related to the attempt to
reprocess an object with
cool
, and usually resulted in an ABEND.
In this release,
cool
marks each object deck as it is processed,
and if an attempt is made to reprocess the marked object, produces a diagnostic
message indicating the condition.
The new processing is divided into two phases. The first
phase marks the output object deck to indicate it has already been processed
with
cool
. It is controlled by the
allowrecool
and
noallowrecool
options. The second phase detects that an input object
deck has been marked to indicate it was previously processed. The second phase
is controlled by the
ignorerecool
and
noignorerecool
options. In Release 6.50, by default,
cool
marks the object
deck to prevent an attempt to reprocess it. Also by default,
cool
detects that the input object deck was previously processed by
cool
.
These defaults can cause
cool
to indicate an error
where it would not detect such an error in previous releases. Under certain
restricted circumstances, it is possible to generate object code that can
be successfully processed by
cool
more than once. If this behavior
is desired, the options can be specified such that the output object's decks
are not marked and that such marking be ignored.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.