I assume that Michael's request, by making this a system variable, would
include a read-only provision, but I'd amend his request to name it,
HPDEFAULTNAMESPACE, to conform to current system variable naming
conventions.  Of course, if and when user-defined system variables are
implemented, this could become a problem.

Lee Gunter
Regence BlueCross BlueShield of Oregon / Regence HMO Oregon
==========================================================
The opinions expressed, here, are mine and mine alone.




From: John Krussel <[log in to unmask]> on 05/07/99 11:36 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: Namespace Enhancement Request




Wouldn't this make it extremely easy to break applications??  Say I was a
vendor and I decided to use the HFS by setting MPEDEFAULTNAMESPACE 3. Then
some user did (quite by accident) a deletevar MPE@, nothing would work!
Wouldn't this be better if it was a change to the HPFOPEN intrinsic itself?