Subject: DC-WG: 3/7 meeting minutes
From: Mark Hahn (mhahn@cadence.com)
Date: Mon Mar 20 2000 - 19:53:01 PST
Meeting minutes from the 3/7/00 DC-WG teleconference
----------------------------------------------------
Attendees:
Mark Hahn, Cadence
Tom Dewey, Mentor
Bob Dilly, IBM
John Paul, IBM
Vikas Sharma, IBM
New action items:
Who When What
---------- ------ --------
1. Tom 3/14 Update the spec with changes
Open action items:
Who When What
---------- ------ --------
Closed action items:
Who When What
---------- ------ --------
1. Tom 3/7 Update the spec with changes
2. Bob 2/29 Test behavior of relative includes
-> 3/7 (source) in TCL, along with handling
of embedded spaces in the file name
for PC compatibility
Next Meeting:
The next meeting will be a teleconference on 3/14/00
from 9-11 am (PDT)
Details:
1. DAC planning
We talked about several options for DAC. There are two conflicting
perspectives, since we've made steady progress but aren't yet ready to
do press releases about the availability of an OVI-approved standard
and release timelines from multiple companies.
On the one hand, it doesn't make sense to invest a lot in DAC
preparations, since any demo or presentations that we would do
would be similar to last year. Given finite bandwidth, it's
better to make more progress on the spec than to rehash the same
message.
On the other hand, if we don't rehash the same message, people
may assume that no progress is being made on the standard.
We agreed that we need to know whether booth space will be
available by the end of March. If there is booth space,
we will prepare a presentation and handouts, but most likely
not do a live demo. At most, we would demo a single tool,
focusing on how users interact with the constraints at the
start of the flow.
2. include command
Bob investigated the behavior of the TCL source command
and found that it interprets relative file names with respect
to the current working directory of the program.
We want the DCDL include command to be relative to the
directory containing the parent file. Mark suggested that
it is feasible and desirable to implement the DCDL include
command as a wrapper around the TCL source commmand, where
the wrapper is responsible for setting up a file scope for
the included file and for setting the right current working
directory in the program.
3. design_name_space command
We agreed that the -characters option should use regular
expression character set notation, and that we should reference
the POSIX 1003.2 standard for this.
We also agreed that there should be a single, consistent set
of rules for escaped characters in general DCDL strings
(those which don't contain design object names). Strings
containing design object names are subject to the escaping
conventions defined by the design_name_space.
Thanks,
Mark
-- Mark Hahn phone: (408) 428-5399 Senior Architect fax: (408) 428-5959 Cadence Design Systems email: mhahn@cadence.com
This archive was generated by hypermail 2b28 : Mon Mar 20 2000 - 19:56:12 PST