Re: [wsbpel] local variables overriding enclosing scope

[Danny van der Rijn <dannyv@tibco.com>]

this appears to be a circular argument.

"It is not permitted to have variables with same name but different
messageType/type/element within an enclosing scope hierarchy..." "...because
an innermost declaration cannot hide outer declarations having different
messageType/type/element"

the inner variable name unambiguously hides the outer one.  why should its
messageType/type/element matter?

----- Original Message ----- 
From: "Ugo Corda" <UCorda@SeeBeyond.com>
To: "Danny van der Rijn" <dannyv@tibco.com>; <wsbpel@lists.oasis-open.org>
Sent: Wednesday, March 03, 2004 4:02 PM
Subject: RE: [wsbpel] local variables overriding enclosing scope


I would imagine that the rationale is the following:

- in the case a variable is referenced in a scope, when multiple
declarations of the same variable with same messageType/type/element
exist in the enclosing scope hierarchy, the reference is unambiguous
because the innermost declaration hides any outer declarations (it's as
if there was only one declaration and all the others were hidden).

- in the case a variable is referenced in a scope, when multiple
declarations of the same variable with different
messageType/type/element exist in the enclosing scope hierarchy, the
reference is ambiguous because an innermost declaration cannot hide
outer declarations having different messageType/type/element, and it is
then unclear which declaration the variable reference is referring to.

Ugo


> -----Original Message-----
> From: Danny van der Rijn [mailto:dannyv@tibco.com]
> Sent: Wednesday, March 03, 2004 3:31 PM
> To: wsbpel@lists.oasis-open.org
> Subject: [wsbpel] local variables overriding enclosing scope
>
>
> in 9.2, it says: "It is not permitted to have variables with
> same name but different messageType/type/element within an
> enclosing scope hierarchy."
>
> can someone explain to me why it is necessary to have this
> restriction?
>
>
> To unsubscribe from this mailing list (and be removed from
> the roster of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/le
ave_workgroup.php.


To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.