HP3000-L Archives

July 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Mon, 8 Jul 1996 12:33:21 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
On Jul 4, 12:31am, Jeff Kell wrote:
> Subject: Re: Sharing Variables
snip...
 
> One possible extension - create new HPCIERR-like variables qualified by PIN
> number, e.g., HPLOCALCIERRORnnn where "nnn" is the PIN of the process.  This
> would let new applications exploit the availability of this function without
> breaking any of the existing applications.  I would suggest "hiding" this
> somehow internally, but this would probably break other things (many existing
> applications query the CIERROR to determine an offspring and/or sibling's
> status).
 
Anyone can create HPCIERRnnn:
  :setvar HPCIERR!HPPIN, value
 
HPPIN is an integer CI predefined variable that contains your PIN.
 
However, 1) you probably should not begin your own variable names with "HP"
and 2) doing this does not remove the window where Process A executes a command
and wants to test HPCIERR, while Process B clears HPCIERR just after
Process A's command executed but before Process A could check the result (or
could make a "local" copy of HPCIERR).
 
Jeff Vance, CSY
 
--

ATOM RSS1 RSS2