| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 108
|
| Category | errata
|
| Synopsis | Only one default clause in config?
|
| State | open
|
| Class | errata-simple
|
| Arrival-Date | Aug 26 2002
|
| Originator | sharp@cadence.com
|
| Release | 2001b Section 13.3.1.2
|
| Environment |
|
| Description |
I don't understand this strange wording: "The use expansion clause (see 13.3.1.6) can not be used with a default selection clause. For other expansion clauses, there can not be more than one default clause which specifies the expansion clause." The second sentence is strange. The term "expansion clause" is not defined anywhere, but seems to refer to use_clause and liblist_clause. Once use_clause is forbidden, that leaves only liblist_clause. If there is only one possible kind of expansion clause, then doesn't this imply only one default clause? Why the bizarre wording of the second sentence instead of just saying "There cannot be more than one default clause." Am I missing something? |
| Fix |
|
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology