Minutes of IEEE P1800 SV-AC meeting #2006-15: 08/29/2006
Written by: Bassam Tabbara

Code for the conference call:

        Domestic:         888-635-9997
        International:    763-315-6815
        Participant code: 2638198

Attendance Record
	Legend:
		x = attended
		- = missed
		r = represented
		. = not yet a member
		v = valid voter (3 out of last 4 or 75% overall)
		n = not valid voter

New PAR, presence record re-initialized on 8/22/2006:

n[--] Faisal Haque (Cisco, Chairman)
v[-x] Eduard Cerny (Synopsys - Co-chair)	
v[xx] John Havlicek (Freescale)
v[xx] Doron Bustan (Freescale)
v[xx] Manisha Kulshrestha (Mentor Graphics)
n[--] Volkan Esen (Infineon)
v[xx] Bassam Tabbara (Synopsys)
v[x-] Hillel Miller (Freescale)
v[-x] Surrendra Dudani (Synopsys)
n[--] Joseph Lu (Altera)
n[--] Yaniv Fais (Freescale)
v[xx] Dmitry Korchemny (Intel)
v[xx] Lisa Piper (Cadence)
v[x-] Jiang Long (Mentor)
==|-------------------------08/29/2006

Agenda:
-------

- Review IEEE working group rules
- Presentation by Dmitry about #1530


Minutes:
--------

- Dmitry went thru "generate.ppt", also "ModulesandFunctions.ppt" until 
slide 21.

- Notes collected by Dmitry (thx Dmitry!), Bassam:

1) The syntax of generate construct should be elaborated. 
Probably, generate should be written explicitly for each generate operator 
inside properties and other construct where confusion is possible. 

2) generate constructs should not be limited to properties, but should 
be extended to other constructs as well (including procedural blocks?) 

3) If the property argument was declared as a sequence, but it is 
actually a Boolean, what will $isboolean return? My preference: 1. [Same
question if argument is typed, tasks intended to return the true nature of arg.
Some reservations expressed about this.]

4) Use different keywords: e.g., like PSL forall for generate constructs inside properties. Counterarguments: if is a natural syntax for conditions; 
what to do in cover groups -- yet another syntax? [Also, generate is familiar 
to Verilog-ers, forall not always meant for replication.]

5) May argument list be empty? If yes, how to process them?

6) Meta language primary purpose is for library building, also useful for 
decompilation (debugging purpose post elaboration of tool-understood user 
intent), not used necessarily in all cases for user-level entry.

7) What is the plan i.e. what's next for these proposals ? Shalom to 
also present to SV-BC after Dmitry collects feedback from AC since many 
of extensions deal with/reflect on assertions. 

8) 2 comments Bassam did not share at meeting:
 - "*" for repeatable args looks like pointer syntax, please 
consider using a variant of "..." or even syntax similar to SVA repetition ...
 - "anytype" can be changed to "implicit" as in the latest type proposal 
discussed.

9) All requested to send feedback to Dmitry.

10) Next meetings: 

 09/05/2006 at 9 am PT (12 pm ET, 5 pm GMT): Regular meeting to deal
 with errata.

====