Simonsen, Larry wrote:
>
> Or what about scripts which act like functions.

Hmmm....

Sounds like what I asked about last April - see:

http://raven.utc.edu/SCRIPTS/WA.EXE?A2=ind9804B&L=hp3000-l&D=&H=&T=&O=&F=&P=11596

(sorry about the wrap-around)

Part of the suggestion I had was:

> Another new variable, HPFUNCTIONPATH, would direct the CI on where
> to look for them.  For instance, I could create a FUNCTION.SYS group
> to keep my User Defined Functions in there, with HPFUNCTIONPATH =
> FUNCTION.SYS.

To which Jeff V. replied:

> I was figuring that HPPATH would still be used to resolve functions
> that are really scripts.  However, there have been a few requests
> for functions that are compiled, exist in an XL somewhere, and are
> invoked by the CI'e evaluator.  An HPFUNCITONPATH that contained
> libraries might be useful.
>
> As with CI pipes, I wouldn't hold my breath for CI functions,
> although personally I'd like very much to add them.

So, I vote with Stan S., Etc.!

 +-------------------------------------------------------------------+
  My mind is my own, as are my ideas and opinions.
  My heart, body, and soul, however, all belong to others.       Tim.
 +-------------------------------------------------------------------+
  Tim Ericson            tericson      DenKor Dental Management Corp.
  Sr. Systems Analyst     at denkor    503-526-4440 (my direct number)
    (& Systems Manager)     dot com         http://www.denkor.com
  Programming HP3000s since 1983!      Quality dental care since 1970!
 +-------------------------------------------------------------------+
  UDCs and Command Files:  http://www.denkor.com/hp3000/command_files
 +-------------------------------------------------------------------+