Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!caen.engin.umich.edu!conliffe
From: conliffe@caen.engin.umich.edu (Darryl C. Conliffe)
Newsgroups: comp.sys.apollo
Subject: Re: Controlling case of returned name from name_$get_path
Summary: What about porting
Keywords: case, help
Message-ID: <45301f87.14df5@ulsoy.engin.umich.edu>
Date: 22 Aug 89 04:00 GMT
References: <45124af7.14df5@ulsoy.engin.umich.edu> <452e55a9.1d6d5@apollo.HP.COM>
Organization: U of M Engineering, Ann Arbor, Mich.
Lines: 20

In article <452e55a9.1d6d5@apollo.HP.COM>, mishkin@apollo.HP.COM (Nathaniel Mishkin) writes:
> In article <45124af7.14df5@ulsoy.engin.umich.edu> conliffe@caen.engin.umich.edu (Darryl C. Conliffe) writes:
> >While using name_$get_path, I find the returned pathname
> >is in all upper case letters.  Does anyone know (1) why,
> >and/or (2) how to get the pathname as it really exists?
> 
> Contrary to a previous, almost correct followup to this posting, the
> correct call to use is "name_$get_path_lc", not "name_$get_path_cc".
> "name_$get_path_cc" (actually all the "_cc" calls) exist only for
> historical reasons -- they got put out before we realized that we really
> wanted all the name-returning calls to take an input parameter that
> specifies the actual length of the caller's output buffer.
> 

Nat, the _cc calls allow me to use them in code to run
on SR 9.7 and SR 10.  The _lc calls are defined only at SR 10.
They don't help me yet! ;=)

>                     -- Nat Mishkin