RE: Proposed Agenda for ISAC meeting 7 September 2006

Chuck,

Re IR2071: I have a note that it was subsumed by FT25, which is implemented
by LCS-2006-109.

Cheers,

PA

--
Dr. Peter J. Ashenden         peter@ashenden.com.au
Ashenden Designs Pty. Ltd.    www.ashenden.com.au
PO Box 640                    VoIP: sip://0871270078@sip.internode.on.net
Stirling, SA 5152             Phone (mobile):  +61 414 70 9106
Australia
 

> -----Original Message-----
> From: owner-isac@server.eda.org 
> [mailto:owner-isac@server.eda.org] On Behalf Of Chuck Swart
> Sent: Wednesday, 6 September 2006 9:39 AM
> To: isac@server.eda.org
> Subject: Proposed Agenda for ISAC meeting 7 September 2006
> 
> 
> Next Meeting: Thursday September 7, 2006, 7 pm Pacific Daylight Time
>                         (Friday September 8, 2006, 2 am GMT)
> 
> 
> telecom info (same as always)
> US 800-637-5822
> Other +1 647-723-3937
> Access Code 6850821
> 
> 1. New ISAC Issues:
> 
> (none)
> 
> 2. Open ISAC Issues:
> 
> 2096    Submitted                       Error is ambiguous
> 2097    Submitted                       Operations with Array 
> aggregates
> 2098    Analyzed        Peter           Ambiguity in 
> definition of T'VAL 
> for Physical types
> 2099    Submitted       Chuck           Alias declarations introduce 
> homographs
> 2100    Submitted                       Operator overloading for 
> protected type methods
> 2101    Submitted       Larry           Type conversion - implicit 
> refers to section 8.1.2 which doesn't exist
> 
> 3.  Review IRs incorportate into Accellera D3.0 LRM
> 
> (attached spreadsheet)
> 
> Note that I couldn't find any reference in LRM or LCSs for
> IR 2071. Can anyone help with this?
> 
> 4. Review of pre-2002 IRs:
> 
> Still to be analyzed:
> 1000 Accumulated typographical and terminology errors.
> 1001 Entity aspect in default binding indication is unclear. 
> 1005 Unclear requirements on prefix in predefined attribute 
> names. 1006 Parentage checks are difficult to verify during 
> static model 
> elaboration.
> 1007 Can a range constraint in a type declaration use 'RANGE? ...
> 
> 
> 
>