Subject: | |
From: | |
Reply To: | |
Date: | Tue, 13 Aug 2002 10:13:23 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Tom writes:
> Actually, "TGAFORMS/FORMS1/FRED" is NOT a "relative" path --
It is if you pass it to a Posix interface, i.e. a c89 compiled/linked
program.
It you pass it to an MPE Intrinsic or CCXL compiled/linked program then it
will assume "MPE escaped" file naming and it will look like the MPE file
TGAFORMS with a lockword of FORMS1.
Ultimately all opens devolve to something like HPFOPEN which has an option
to say how the filename should be interpreted.
Most libraries use the MPE escaped option which says that if the name starts
with a dot "." or a slash "/" then it is a Posix name, otherwise it's an MPE
name. The notable exception are the Posix libraries and by extension GCC
and c89 programs *and* most programs compiled using them (Apache, Samba,
etc.), which specify Posix-only which means that A/B will be treated as a
Posix path rather than an MPE filename/lockword.
There's also an option for MPE-only syntax, though offhand I can't think of
anything that commonly uses this, since normal MPE names don't start with a
. or a / and so you and almost always use MPE escaped syntax for any MPEish
program but you generally have to use Posix-only for programs that
originated on non-MPE platforms to keep from breaking them.
The CCXL command and its related link variants are a little odd in that they
predate the Posix subsystem and so do the best job they can of compiling C
programs without any knowledge of the Posix world. This means that CCXL
generally leaves you with a pure MPE program using MPE semantics for
everything.
G.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|