HP3000-L Archives

August 2001, Week 4

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: CI Programming talk on Jazz
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Tue, 28 Aug 2001 18:58:09 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines) 
...
> I asked Jeff during that presentation how the !HPFILE
> variable is affected by symbolic links.  The answer is
> that !HPFILE gives the actual file being run,
> not the symbolic link.

This answer was my best guess at the time of the talk.  I
just verified (as I assume Ted did already) that this is
in fact correct.  HPFILE is a simple interface to the
FFILEINFO intrinsic and passes a file number, not a name.
The symlink resolution really occurs when the CI opens the
file by calling FOPEN on the symlink name. FOPEN follows the
symbolic link, opens the target file, and returns a file number.
FFILEINFO accepts this file number and returns the qualified
primary name.

 Jeff V.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2