Subject: | |
From: | |
Reply To: | |
Date: | Tue, 20 Feb 2001 13:04:52 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Following from what John wrote below, if you do
:SETVAR TRUE FALSE
and you have already done
:SETVAR FALSE TRUE
the situation fixes itself. (Obviously not the preferred solution, since it
only works when you're explicitly setting a Boolean value, but there's more
than one way to skin a cat.) Wow, you could cause a lot of trouble doing
this!
Patrick (suddenly the song "Yes, We Have No Bananas" is playing in my head
-- coincidence?)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Patrick Santucci
HP e3000 Systems Administrator
Cornerstone Consolidated Services Group, Inc.
> -----Original Message-----
> From: John Clogg [SMTP:[log in to unmask]]
> Sent: Tuesday, February 20, 2001 12:45 pm
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Scratching my head; boolean variables always
> TRUE
>
> The only thing I could think of would be if a Boolean variable named
> FALSE,
> with a value of TRUE exists for your session.
>
> -----Original Message-----
> From: John Pollard [mailto:[log in to unmask]]
> Sent: Tuesday, February 20, 2001 9:38 AM
> To: [log in to unmask]
> Subject: Scratching my head; boolean variables always TRUE
>
>
> I recently encountered a situation that I simply can not explain. In
> certain situations, my session becomes unable to set a boolean variable to
> FALSE. Doesn't matter if it is a CI variable like HPCMDTRACE or one of my
> own creation. Doesn't matter if already existed or was created for the
> first time by my "setvar".
>
> I can do the following:
>
> SETVAR ISITSO,FALSE
> SHOWVAR ISITSO
>
> and the result is:
> ISITSO = TRUE
>
> How could this ever happen?
>
> Possible background info:
> This just began happening after I started testing a demo of a product
> mentioned on this list, namely: ScreenJet. I am not pointing any fingers
> here; coincidences happen all the time. I have submitted this question to
> the makers of ScreenJet, but thought I would run it by the astute members
> of this list; since I could not conceive how anything could cause this
> phenomenon to occur.
|
|
|