"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 02/24/2005 06:40:32 PM:
[snip /]
>
> It looks like it's there as a macro on v7.3-1:
>
>
> $ sea sys$common:[decc$lib.reference.sys$starlet_c]*.h fab$v_erl
>
> ******************************
> SYS$COMMON:[DECC$LIB.REFERENCE.SYS$STARLET_C]FABDEF.H;3
>
> unsigned fab$v_erl : 1; /* Erase Regardless of Lock */
> #define fab$v_erl fab$r_fop_bits_overlay.fab$v_erl
> unsigned fab$v_erl : 1; /* Erase Regardless of Lock */
> #define fab$v_erl fab$r_fop_overlay.fab$r_fop_bits_overlay.fab$v_erl
>
YES!!!! It looks to me like the
#define fab$v_erl fab$r_fop_overlay.fab$r_fop_bits_overlay.fab$v_erl
is all I need for the patch to work for me (under 7.1) without subtly
breaking the functionality under systems that actually support this bit.
Both a bit mask _and_ a macro. How quantum.
Anyhow, it looks to me again like the published patch should be good.
Though I hope Peter (or someone who has 7.3 - maybe Nico, since he failed
to confirm Craig's finding?) will actually set this bit on a file and
confirm that the patched VMS::Stat returns TRUE.
Sorry to involve the mailing list in my dithering, and thank you very much
Craig for providing me the confirmation I needed.
Have I thoroughly confused the issue? Should I republish the patch? It's
the same as yesterday, it's just that yesterday afternoon I thought it was
bad, and now I'm convinced it's OK.
Tom Wyant
PS to Nico, but really to everyone -
My original dithering was because I was conscious of the definitions like
unsigned fab$v_erl : 1; /* Erase Regardless of Lock */
which are _not_ macros. The macros Craig found were farther down. The
doubled hits were because of a conditionalization on __NEW_STARLET.
TRW
This communication is for use by the intended recipient and contains
information that may be privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender
by return e-mail and delete this e-mail from your system. Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer. This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.
Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean
http://www.DuPont.com/corp/email_disclaimer.html
