Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!UIAMVS!ADPDKHTS
From: ADPDKHTS@UIAMVS.BITNET (Deb Hawley 319-335-6321)
Newsgroups: bit.listserv.sas-l
Subject: Re: Compiled SAS code
Message-ID: <SAS-L%90011116424900@MARIST.BITNET>
Date: 11 Jan 90 21:30:00 GMT
Sender: "SAS(r) Discussion" <SAS-L@OHSTVMA>
Reply-To: Deb Hawley 319-335-6321 <ADPDKHTS@UIAMVS>
Lines: 20
Approved: NETNEWS@PSUVM Gateway

>
> The object code does not have external references resolved, and
> there are some other unresolved references, too.  This is what
> is stored by the Stored Program Facility.
>

     I apologize to the list if this is too technical of a question,
     but I can't help but think others might be interested, too.

     If SAS can handle unresolved references as you suggest, why
     did they stop with just the DATA step?  There's no reason why
     references couldn't be resolved at run time to a library
     containing the SAS procs? (instead of copying in the entire
     thing and storing it in object code, as someone mentioned that
     was the reason SAS didn't include PROCS).  That's the way I
     understand our PL/I libraries to work.  Can you explain more?

     Deb Hawley
     Systems Programmer
     University of Iowa