Re: conflicting variables (was Re: Pro*C - extra space after variables)

From: Kenneth C Stahl <BlueSax_at_Unforgettable.com>
Date: Fri, 10 Dec 1999 07:40:12 -0500
Message-ID: <3850F4AC.D9088E9C_at_Unforgettable.com>


Clint Eastwood wrote:
>
> Thomas
>
> In article <u8qv4sg8npulosqr57q69fsdlh6gvuoevk_at_4ax.com>,
> tkyte_at_us.oracle.com wrote:
> >You had it as a global in your sample so yes (borrowing from your example),
> >absolutely I want it static so it does not conflict with other peoples
> >variables. Your code had:
>
> I had not considered this issue befor, and it seems quite important.
> Does this mean that in a situation where several instances of the Pro*C
> code is running, that the variables in the code that are global will
> conflict with each other??
>
> I would have thought that they would each have their own uarea and that
> they shouldn't, however I had assumed that this would also be the same
> on the server side.
>
> so IF I have a global flag in a ProC program, does this mean that if
> more than one instance is running (we are writing an API for a CGI) that
> they could conflict in the database???

You can rest easy. Even if two different pids share text they do not share data - unless they are both using a specifically allocated shared memory segment. Received on Fri Dec 10 1999 - 13:40:12 CET

Original text of this message