Next Meeting: Thursday, March 01, 2007, 6 pm Pacific Time (Friday, March 02, 2007, 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: 2099 Analyzed Chuck Alias declarations introduce homographs John Ries has commented on some aspects of this issue. I will submit material before the meeting. 3. Review of IRs incorporated into D3.0 LRM: 2058 2006-028 Ajay 2074 2006-033 Chuck OK 2075 2006-038 Chuck OK 2077 2006-034 Ajay 2078 2006-035 Ajay 2079 2006-041 Lance 2080 2006-039 Lance 2081 2006-040 Larry 2082 2006-046 Larry 4. Review of pre-2002 IRs 1000 Peter 1047 Chuck Open Issues Remain 1048 Chuck Open Issues Remain 1049 Ajay 1050 Ajay 1051 Lance 1052 Lance 1055 Larry 1056 Larry D3.0 IRs to be assigned: 2083 2006-042 2084 2006-043 2086 2006-047 2087 2006-044 2090 2006-045 2092 2006-048 2093 2006-049 2094 2006-050 2095 2006-051 Pre-2002 IRs to be assigned/evaluated: 1057 Expanded names are not allowed in extended regions. 1058 What use are LINKAGE ports? 1059 What is the allowed use of others in record aggregates? 1060 A'LEFT's result type is anomalously described. 1062 Can a resolution function return an unconstrained array? 1063 Scope and visibility rules for predefined attributes are unclear. 1064 Passiveness of processes is not analysis-time computable. 1066 Conversion function definition assumes different types. 1069 Mod and rem are ill-defined when they return zero. 1070 VPI Issue 14 -- Prefixes in USE clauses 1071 The bounds of array aggregates are ill-defined. 1072 Does the elaboration of a process statement create a process? 1074 Interpretation of overloaded name prefixes is unclear. 1075 Self-referential access types are not prohibited. 1076 Applicability of resolution functions is still unclear. 1077 Out ports cannot drive buffer ports. 1079 Conflicting rules for direction of concatenation 1081 Expression elaboration with impure functions 1082 Implicit conversion of a universal real expression 1085 "Staticness" of the predefined attribute INSTANCE_NAME 1086 Use of character literal or operator symbol in alias 1088 Problems with physical mapping of libraries 1089 Visibility problem with components and USE clauses 1090 Do library clauses extend from entities to architectures? 1091 Group constituent names cannot have signatures. 1092 Must a selected name in a use clause denote anything? 1093 Replacement characters (from Ada) complicate parsing. 1094 Bad wording for individual association for subprograms. 1095 Are time literals with real numeric parts exact? 1096 Entity aspect poorly defined for incremental binding. 1097 Why do primary unit names in secondary units differ? 1098 Can variable parameters be left unassociated or not? 1104 Inconsistent, overly restrictive subtype checks. 1105 The elaboration of group declarations is not defined. 1106 Accumulated problems with unclear wording. 1107 Postponed process behave illogically at initialization. 1108 The subtype of a deferred constant may not always be deduced during analysis time. 1109 The term "named entity" it not defined. 1110 The term "object" is not well-defined. 1111 Is a user-defined attribute an object? 1112 Need to disallow conversion function signal parameters. 1114 LRM wording doesn't account for separators. 1115 Should subtype and constraint checks really be made when the driver takes on the value of a signal? 1116 implicit signals in guard expression (via port maps) 1117 Problem with Composite Resolved Signal 1118 Group constituent can't be user-defined attribute name. 1119 LRM is not clear as to when the wait statement condition clause is evaluated in a postponed process. 1120 Inconsistency about the mode of formal parameters of class file. 1121 Meaning of a changed value for reals is not clear 1122 Default binding text and examples disagree 1123 Simulation cycle does not account for processes resuming after expiration of the timeout interval 1124 Are all actuals evaluated in incremental binding? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Feb 28 17:22:22 2007
This archive was generated by hypermail 2.1.8 : Wed Feb 28 2007 - 17:22:24 PST