Phone Conference P1450.1 Working Doc Subgroup
Thurs December 4, 10:00 am PST
Attendees:
Tony Taylor (chair)
Julie Villar
Greg Maston (scribe)
John Cosley
Dan Fan
Peter Wohl
Documents
http://grouper.ieee.org/groups/1450/private/p1450.1-D17.pdf
(latest working draft)
http://grouper.ieee.org/groups/1450/dot1/p1450.1-D17-review-resolution.pdf
(issues & resolutions)
http://grouper.ieee.org/groups/1450/private/p1450.1-D17-code.txt - code
Agenda
1. Review (and hopefully
approve) all changes to D17.
DM-3 - NameMaps for ScanCells (clause 17.4)
DM-4 - New write up on parameter passing (clause 20.2)
JC-2 - New changes to expressions (clause 6.2)
TT-2 - New change to LoopData as consequence of JC-2 (clause 19.4)
2. Ballot status
3. Any further issues prior to ballot?
4. Code file available on the web.
Meeting discussion
IEEE meeting clearances
Nothing under discussion or presentation for this meeting was identified
as being proprietary or restricted.
Ballot List
43 people on list, a handful are ineligible. John Cosley worked through
some issues with the IEEE and should have fixed his ineligible issues.
NameMaps
Proposal was presented last time and left open for additional review.
Accepted with no objections.
Expressions
To eliminate expression ambiguity and reduce the burden of single-quoting,
expression operators have now been differentiated between expression
types. This makes the context of the operation immediately determined from
the expression itself, and not dependent on evaluating the 'type' of the
names present in the expression (which cannot be established in STIL until
actual run-time context through the PatternExec et al.)
This proposal was accepted with no objections. There were several
subsequent discussions here:
page 13 - has 3 "section "a)"'s in it. Tony [AI1].
third section "a)" on page 13 - has an example showing a Loop with a
Boolean expression. Clause 19.1 shows boolean_expr in the Loop statement
as well but does not define the handling of this expression type. Because
the While statement supports this construct directly (and obviously), the
Working Group agreed to remove the boolean_expr from the Loop statement
and allow it for While statements only. [AI2] to Tony to change example on
pg 13 and remove boolean_expr from Loop in section 19.1.
Question about '0x' - This is documented in table 5.
Question about the statement "bare integer allowed with or without quotes"
- Are quotes truly optional? Should make that statement. Tony [AI3] to
make the statement that quotes are optional around single integers.
example line 197, page 21 - currently uses the multiple assignments form.
This raised some concern as the multiple assignment form has minimal
documentation, and while it is not wrong here, in the interest of
providing consistent examples it will be changed to a single-assignment
form which is also correct and more often used, Tony [AI4].
LoopData and Shifts - Question was raised about the different forms of
parameters supported in dot1 for these operators. In dot-0, Shift
constructs use '#' to absorb subsequent values through iteration, but in
dot-1 there is an option to specify a "constant string" which itself may
contain signalvariable references that are evaluated once on entry to the
block and establish a fixed length (and value) of data to be applied in
that context. Request was made for additional clarification of this
behavior, which will be handled as a ballot issue. [AI6] TBD - Suggestion
is to create a new sub-clause which supplements STIL.0-clause 24. Tony
will add this to the new D18 list of resolutions as the first ballot issue
to be addressed.
Concern - about the ability to declare non-contiguous groups by
specification of individual elements, for instance 'Signals { "A"[0 2 3]
In; }' Previous discussions disallowed non-contiguous groups. A
clarification that ONLY the ellipsis operator is supported for signal and
group declarations was requested. [AI5] to Tony.
Loop Data
Because variables do not require quotes, it is ambiguous whether Data is a
token or a variable reference in the construct "Loop Data". To eliminate
this ambiguity, proposal to change Loop Data to LoopData. No objections.
Code examples
Code examples from the working specs for .1 and .3 are available on the
website as text documents.
Next Actions
Final draft 18 with changes identified below to be sent to the IEEE for
balloting. Next meeting in two weeks - Dec 18, 10:00 PST to discuss any
issues with the process.
Meeting adjourned at 11:03 pm PST.
Next meeting
Thursday, Dec 18, 2003, 10:00 to 11:30AM, PST
AIs
[AI1] Tony - page 13 has 3
"section "a)"'s in it.
[AI2] Tony - page 13, clause 19.1 eliminate bool_expr in Loop
[AI3] Tony - statement that quotes are optional around single integers
[AI4] Tony - page 21, line 197, change to single-assignment form.
[AI5] Tony - identify ellipsis operator ONLY for signal/group
declaration.
[AI6] TBD - Suggestion is to create a new sub-clause which supplements STIL.0-clause 24. Tony will add this to the new D18 list of resolutions as the first ballot issue to be addressed.