[sv-ec] April-15-2005 discussions

Hi,
I have arranged the following items in order of what
I think we can review today.
- Mehdi

==========================

Issue #	Mantis #
233	?   (Surrendra - from sv-ac chair)  bit-streaming of classes

235  666  pass by ref for static tasks
      http://www.eda.org/svdb/bug_view_page.php?bug_id=0000666
      http://www.eda.org/svdb/file_download.php?file_id=809&type=bug


236	642 (duplicate 411)	scope for default expressions
      http://www.eda.org/svdb/bug_view_page.php?bug_id=0000642
    (also take a look at item 10, mantis 409)

238  ? (Ray)  using clocking block
	Informative note only

240  ?  (Arturo)  semantics of class


***** From sv-bc: for EC review
1   93  Optional argument list for subroutine calls  [tasks() and
func()] 
      http://www.eda.org/svdb/bug_view_page.php?bug_id=0000093
	[look at the bug notes for more explaination]

244  632   Hierarchical reference in interface port connection
	[approved in SV-BC 4/11/05;  for sv-ec to review and comment if
necessary]
    http://www.eda.org/svdb/bug_view_page.php?bug_id=0000632
    Section 20.2
       At the end of 20.2, ADD
         If the actual of an interface port connection is a hierarchical

         reference to an interface or a modport of a hierarchically 
         referenced interface, the hierarchical reference shall refer to
an 
         interface instance and shall not resolve through an arrayed 
         instance or a generate block.

229  644   
   [Was passed in sv-ec, but sv-bc reviewed and failed]
 
     The SV-BC reviewed the proposal to address issue 229 in
     its April 11th meeting.  It was not approved.  Here's
     the message that the committee agreed to convey
      to the EC:

      The SV-BC did not pass the proposed resolution to issue
      229 as captured in Mantis #644.  The motion failed 
      with only abstention.


    Those abstaining felt that making such a change so late
    in the lifecycle of the LRM was not a good idea.  They
    had concerns about issues such as:
    -continuous assignment to variables
    -initializer passed with with Type through parameters
      which is a new paradigm.


283   615   multi-dimensional arrays
    [was passed in sv-ec, with 3 abstains, 1 no vote, 
		champions had some concerns]
     There were 3 champions that gave the following feedback.
      http://www.eda.org/sv/sv-champions/Resolved_Issues_05_04_11.htm
      Need to reword first sentence of 5.6:
        One or dimensions of an array or queue can be dynamic...
        Add 2 dimensional example.
      We should consider making these changes. Stu said that he thinks
that
      the BNF change is now in conflict with the text.
----------------------------------------------------------------------
281   ?		mailbox return value  (-1,1 vs negative, positive 


  2    219   (disable/fork-join item)
  5    319   (root thread)
  7    344   (
  8    370   ( chap 13.13  seed/RNG)
 10    409   (ref arguments, should be taken care of  with item 236

 22    514   ( type for mailbox )
 36    270   (enhancement -- randomize)

 -- queues/concatenation)
 13    412
 23    517
 24    520

  -- program/scheduling semantics)
 30    549 
 41    551
 32    553

 
-----------------------
	94	511	( type assignments)
	95	512	(object copying)
	96	516	(type compatiblity description)

	97	518	( queues, arrays, page 51)
	98	519	( empty array 
	99	521	( queues, pattern assignment)
	100	522	( queues concatenation)
	101	523	( queue return type)	
		

	122	251	(enhancemet -- coverage)  	
	123	253	( coverage)
	162	552	( coverage -- BNF update)
		  		
	171	564	(cross program references)

	187	594	( interface access through clocking block)
	188	595	(invalid example clocking block assignemnt --
proposal)
	190	597	(unnamed cloking blocks in bnf)
	199	607	(accessing values in cloking block)
	200	608	(clocking block value resolution)
	201	609	(##cycle meaning in 16.14