Issue - 101 - Proposal to vote

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

following discussion at the F2F this morning, my proposal is as follows:

- remove the following from 9.2: "It is not permitted to have variables with
same name but different messageType/type/element within an enclosing scope
hierarchy."
- add the following:  "Variable access follows common lexical scoping rules.
A variable resolves to the nearest enclosing scope, regardless of the type
of the variable."

----- Original Message ----- 
From: "ws-bpel issues list editor" <peter.furniss@choreology.com>
To: <wsbpel@lists.oasis-open.org>
Sent: Friday, March 05, 2004 11:37 AM
Subject: [wsbpel] Issue - 101 - Local variables overriding enclosing scope


This issue has been added to the wsbpel issue list. The issues list is
posted as a Technical Committee document to the OASIS WSBPEL TC pages on a
regular basis. The current edition, as a TC document, is the most recent
document with the title in the "Issues" folder of the WSBPEL TC document
list - the next posting will include this issue. The list editor's working
copy, which will normally include an issue when it is announced, is
available at this constant URL.

Issue - 101 - Local variables overriding enclosing scope
Status: open
Date added: 5 Mar 2004
Submitter: Danny van der Rijn
Date submitted: 04 March 2004
Description: 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." This seems to be unnecessarily restrictive, and inconsistent
with scoping behavior in other languages.
Submitter's proposal: remove the restriction
Links: Danny van der Rijn, 3 Mar 2004     Ugo Corda, 3 Mar 2004     Danny
van der Rijn, 3 Mar 2004     Ugo Corda, 4 Mar 2004     Yuzo Fujishima, 4 Mar
2004     Yaron Y. Goland, 4 Mar 2004     Chris Keller, 4 Mar 2004     Danny
van der Rijn, 4 Mar 2004
Changes: 5 Mar 2004 - new issue

----------------------------------------------------------------------------
----

To comment on this issue, please follow-up to this announcement on the
wsbpel@lists.oasis-open.org list (replying to this message should
automatically send your message to that list), or ensure the subject line as
you send it starts "Issue - 101 - [anything]" or is a reply to such a
message.

To add a new issue, see the issues procedures document (but the address for
new issue submission is the sender of this announcement).

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.