Issue - 265 - Preventing explicit declaration of forEach counter variable

[ws-bpel issues list editor <peter.furniss@erebor.co.uk>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document 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 - 265 - Preventing explicit declaration of forEach counter variable

Status: received
Date added: 14 Apr 2006
Date submitted: 13 April 2006
Submitter: Mark Ford
Description: The <forEach> activity implicitly creates a variable within its associated scope. Variable names within a scope must be unique so it would be an error to have a variable declared within the forEach's scope with the same name as the implicit counter variable. We have a similar statement for implicit variables within an onEvent. This same language should be used in the forEach section.
Submitter's proposal: Something along the lines of: 
> If a variable of the same name as the forEach counterName is declared explicitly in the enclosed scope, it would be considered a case of duplicate variable declaration and MUST be reported as an error during static analysis. 

Changes: 14 Apr 2006 - new issue

---

To comment on this issue (including whether it should be accepted), 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 - 265 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - 265 - Proposed resolution", without any Re: or similar.

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