Priorities, disposition etc. and comments

Here are my priorities etc. for the remaining issues (37-50).

37. Expression Type Classes -- capitalization convention

     Prio: 5

38. Parameters of more types should be supported.

     Prio: 5

     This is intimately connected to (albeit first level) property IP
     reusage.

39. Clarify input sampling mechanism.

     Prio: 5

40. Clocking of endpoints, prev etc.

     Prio: 5

41. Generalization of forall (and forsome) to work on all "levels".

     Prio: 5

42. Data-oriented coverage

     I would need a more concrete proposal to say anything definite about
     this. Certainly, I agree that data-oriented coverage support is
     missing in PSL. However, how does this issue relate to forall on
     directive level for instance, to enable things like

        forall st in StateType : cover { state_reg = st };

     Prio: ?

43. Transaction-oriented coverage

     Prio: 0

44. SystemC flavor

     Prio: 4

45. Clarify that time is discrete

     LRM issue

     Not sure if this is necessary...

     Prio: 1

46. Clarify that time is context-independent

     LRM issue

     Prio: 1

47. Typed forall

     Extension

     Prio: 4

48. Clarify explanation of clock expressions

     LRM

     Prio: 3

49. Assertion Control Capability

     Extension

     Prio: 0

50. Parameterized AND/OR operators

     Extension

     I think the idea is OK, but that we certainly don't need both this
     variant and forall, in case issue 41 is granted. It depends also on
     what can be expressed with these new constructs in terms of
     repetition range for instance (see also issue 47).

     Prio: 0

Best regards,

Johan Alfredsson Mobile: +46 706 39 12 58
Product Manager Office: +46 31 745 19 00
Safelogic Fax: +46 31 745 19 39
Arvid Hedvalls Backe 4 johan.alfredsson@safelogic.se
411 33 Göteborg, Sweden www.safelogic.se
Received on Tue Nov 30 06:56:33 2004