Attendees:
Mark Hahn, Cadence
Tom Dewey, Mentor
Bob Dilly, IBM
Jim Engel, IBM
Vikas Sharma, IBM
New action items:
Who When What
---------- ------ --------
1. Tom 11/30 Complete updates to 0.1.2 spec from review
2. Mark 11/30 Investigate issue tracking mechanisms for
the web site
Open action items:
Who When What
---------- ------ --------
1. Vikas 11/9 Review derived_waveform and derived_clock
-> 11/30 commands, try to convert Einstimer example
to them
2. Bob 11/16 Send Mark contact info for Magma
-> 11/30
Closed action items:
Who When What
---------- ------ --------
1. Tom 11/16 Complete updates to 0.1.1 spec from review
2. Tom 11/16 Investigate ways to automatically extract
examples from the document
Next Meeting:
The next meeting will be a teleconference on 12/14
from 9-11 am (PDT):
(310) 914-4300, passcode 5637 #
Details:
1. Review action items
No progress on the Magma contact yet, Bob will pursue by the
end of the day 11/16. Vikas looked at the derived clocks commands
but wasn't sure whether they fully support the semantics required
by the Eimstimer commands from the example circulated several meetings
ago. He will try to convert the example into DCDL.
2. Review changes reflected in version 0.1.2 from last week's
review of pages 19-26, and pages 26-33
We talked quite a bit about white space, quoting strings versus
quoting special characters, and the use of curly braces "{}" for
enclosing lists versus strict quoting. We agreed that
- newlines are command terminators, not whitespace
- double quotes will be used for string arguments
- special characters will be escaped according to the
rules of the selected namespace (rather than by curly braces)
Lists will be enclosed in curly braces, and list elements
will be separated by white space. Due to the possibility of
embedded whitespace and other special characters within a design
object's name, applications must parse the list explicitly according
to the selected namespace's rules, rather than relying on the Tcl
list commands.
3. Discuss derived clocks
4. Discuss schedule and technical editing requirements
We again ran out of time to discuss these.
5. Misc.
We talked about how to more efficiently review changes, and
agreed to comment on previously discussed changes just through
email, focusing on new sections during the teleconferences.
Thanks,
Mark