Meeting Sept. 27, 2004
Attendance
Steve Bailey
Jim Lewis
John Ries
Charlie Guy	
Chuck Swart

FT20
Lots of confusion about how the choice gets expanded and it the
bit reversal operation. 

Possible modifications:

1) Range of choice is ignored if actual is the same type as the sub-elements subtype.
   But if actual is of the array type then the direction of range must match.

   
2) Direction of choice is ignored, the bounds is taken from choice and the direction
   is take from the expression's type.

3) expand notation, 'element attribute, but has problem with expressions and mapping
  in named association.

4) Eric proposal to relax type checking rules so we are just doing in-order traversal
of type of left and right hand-side and doing the assignment on each scalar sub-element
that must match in type.

  Chuck this appears to have may problems in current type system.

Modification of item J has problems when left hand side is a slice, no subtype is
is defined, 


Action item for John
 1) Add impact on overload rules 
 2) Resolve meaning of 0 to 3 for choice
 3) Asses cost of ambiguity, leave or change overload resolution rules
 

FT27
  Issue how to pick only entity when architectures are present?
  Eric -> if entity has architecture, user cannot select entity only.

  Chuck issue of architecture being block within entity, 2002 standard,
  or all in one block. Steve and Chuck believe the consensus was to back
  this change out.  Chuck will see if there is an IR and consult with
  ISAC members.

  John motions as being Done.
  Jim will mark as done.

  Eric proposed that why not allow architecture without a name. 
  Steve: next version of proposal.