Re: ARCH_NAME nomenclature question
From: Hoff Hoffman (hoff_at_hp.nospam)
Date: 09/06/05
- Next message: WhoDat?: "Re: VAXen as a plural of VAX"
- Previous message: David Jones: "Re: Has HP Forgotten?"
- In reply to: JF Mezei: "ARCH_NAME nomenclature question"
- Next in thread: JF Mezei: "Re: ARCH_NAME nomenclature question"
- Reply: JF Mezei: "Re: ARCH_NAME nomenclature question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 06 Sep 2005 17:08:34 GMT
In article <431BDBC9.E508137E@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:
:Is there an assurance that f$getsyi("ARCH_NAME") will always return a
:value that can be used to build a symbol name or a file name on ODS2
:disks ?
:
:(eg: no spaces, limited to digits and letters) ?
I am aware of no such guarantees within the OpenVMS documentation.
If this sort of construct is a consideration within within your DCL
symbols or other such code, do consider an alternative -- such as the
use of f$getsyi("ARCH_TYPE") -- instead.
:For instance, a few years ago, arch_name for that IA64 thing was
:supposed to be "IA-64" but changed to "IA64". Had it remained at IA-64,
:some DCL would break:
:$library_'f$getsyi("ARCH_NAME")' = "mylibrary_''f$getsyi("ARCH_NAME")'.OLB"
I was the one that provided the original text for the documentation for
the return string -- to allow folks some basis to start the port -- but
it was subsequently decided -- after the earliest documentation shipped
and before the code and the full documentation was shipped out -- to
change the returned string to keep it entirely alphanumeric.
I do regularly use f$getsyi("ARCH_NAME") within filenames, but I tend
to follow a subset approach with my use of DCL symbols.
--
And as I expect this is really a troll seeking to extract information
and/or to generate follow-up postings, and that this has nothing to do
with the question actually posed, I am aware of no plans to port OpenVMS
to any new platforms.
I am aware of no plans for a native port of OpenVMS for Power, EM64T,
AMD64 or other 64 bit platform.
I'd be personally flabbergasted if there were ever any future porting
plans ever even remotely considered for a port backwards to a 32-bit
platform. To any 32-bit platform. But again, I am aware of no plans
for any new OpenVMS port -- to any platform, whether 8-, 16-, 32-, 64-
or 128-bit, or otherwise.
Intel Itanium is the path forward for OpenVMS 64-bit computing.
---------------------------- #include <rtfaq.h> -----------------------------
For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com
- Next message: WhoDat?: "Re: VAXen as a plural of VAX"
- Previous message: David Jones: "Re: Has HP Forgotten?"
- In reply to: JF Mezei: "ARCH_NAME nomenclature question"
- Next in thread: JF Mezei: "Re: ARCH_NAME nomenclature question"
- Reply: JF Mezei: "Re: ARCH_NAME nomenclature question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|