Subject: strategy for DirectC
From: Andrzej Litwiniuk (Andrzej.Litwiniuk@synopsys.com)
Date: Thu Dec 12 2002 - 10:02:12 PST
Swapnajit & Ghassan,
Do you have a strategy for dealing with a deadlock? Kind of Plan B?
What if we, the team, fail to provide a palatable solution?
I don't mean here the differences of opinions nor conflicts of preferences
for alternative solutions.
Those conflicts/differences can be dealt with via negotiations or through
the voting process. I don't see any evil in diversified views or needs.
And I understand and accept that such a diversification means that some
people will be more satisfied with the outcome than others.
I'm worried, however, how we will proceed if we don't solve technical issues
in a satisfactory way in the alloted timeframe?
[Note: "satisfactory" is a subjective term.]
Maybe the bar is too high and we'll have to lower our expectations.
Sometimes technical issues are plain hard. Or a perfect solution simply does
not exist. Or is hard to find.
Sometimes people tend to not accept facts, like that something is undoable
or doesn't come for free, or that there is a trade-off and one cannot have
two conflicting things at the same time. (Personally, I'm frustrated that I
cannot see any solution that would grant binary compatibility, would impose
no restrictions upon simulator and would not involve any overhead for arguments
copying, yet would provide elegant access to SV objects using SV indexing in
C code.)
If there are alternative partial and imperfect solutions, shall we consult
the requirements to guide us in the decision making process?
Maybe the initial requirements need a revisit? (Or a revision?)
Maybe more time is needed. Maybe a lame solution has to be accepted?
I don't know.
Regards,
Andrzej I. Litwiniuk
==============================================================================
Andrzej I. Litwiniuk, PhD Principal Engineer VCS R&D
Synopsys, Inc TEL: (508) 263-8056
154 Crane Meadow Road, Suite 300, FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================
This archive was generated by hypermail 2b28 : Thu Dec 12 2002 - 10:02:44 PST