Article View: gnu.emacs.vms
Article #28VMSFNS
From: nli!jym
Date: Wed, 19 Jul 1989 18:04
Date: Wed, 19 Jul 1989 18:04
23 lines
1357 bytes
1357 bytes
Well, it looks like others (Bruce Skinner _et_al_) have explained the
changes to the facility$V_keyword things. The general rule is something
like this:
facilty$M_keyword = (1 << facility$V_keyword);
However, all the facility$V_keyword constants were turned into bitfields
by our compatibility-conscious friends at DEC.
A quick and easy way to find out a facility$V_keyword value is to do
this (using PRVDEF as an example):
$ library/macro/extract=$PRVDEF/output=tt: sys$library:STARLET
This will show (in MACRO) all the facilty$M_keywords and also the
facility$V_keywords. Then you can do a quick and dirty #define.
If you need something that doesn't have a .H file for it, you can also
yank it out of STARLET.MLB, but redirecting the output to another file.
(In the above example, you'd use "/output=PRVDEF.H" to do this.) Then
you can edit the file and turn Macroese into C (real easy with Emacs'
keyboard macros).
<_Jym_>
Technical Details
Message-ID:
<8907191804.AA02862@nlp9>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!APPLE.COM!nli!jymReferences:
<8907182344.AA04247@apple.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!APPLE.COM!nli!jym From: nli!jym@APPLE.COM Newsgroups: gnu.emacs.vms Subject: VMSFNS Message-ID: <8907191804.AA02862@nlp9> Date: 19 Jul 89 18:04:50 GMT References: <8907182344.AA04247@apple.com> Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 23