ISAC: Proposed Agenda for ISAC meeting 17 July 2008

From: Chuck Swart - MTI <cswart_at_.....>
Date: Wed Jul 16 2008 - 18:34:37 PDT
Next meeting:  Thursday, July 17, 2008, 7 am Pacific Daylight time.
              (Thursday, July 17, 2008, 2 pm GMT)

Telecon info (same as always)
US 800-637-5822
Other +1 647-723-3937
Access Code 6850821

This agenda will need to be flexible and is intended to get the next 
draft LRM into circulation
ASAP.

1. Review of draft ballot resolution document

2. Review of pre-circulation LRM version D4.3

3. "New Bugzilla issues"

249  Ballot comments from Alex Zamfirescu
250  Extension of generate statements makes language too complex
251  New introduction needed
252   Typo in 24.1.1
253   Confusing terminology in 24.1.1

Verify new resolved issues:

208 D4.2 simple typos
209  Line numbers don't align
210  ?? for STD_ULOGIC still listed in table in 9.2.9
211  Confusing rules for object aliases.
212  Inconsistent treatment for PSL declarations
213  Can a force signal assignment update ports of mode IN?
214  Semantics of some READ procedures are not complete
215  Problem with deallocation of lines in textio.
216  Clause title on VHDL-87 is out of date.
217 Confusing/contradictory requirements for viewport objects
218  Permitted access into encrypted code unclear
219  What directives can appear in encrypted source text and ...
220  Inconsistent use of vhpiIntT and int
221  Unclear descriptions of VHPI_SENS_ISSET and VHPI_SENS_FIRST
222  condition expression should be boolean
223  Contradictory statements about normative status of 1164 b...
224  In glossary, some references are out of order.
225  Glossary description of complete context is no longer cor...
226  glossary entry for "design unit" is no longer correct
227  glossary entry for expanded name has incorrect reference
228  Glossary entry for floating-point type is incorrect
229  Is type vhpiIntT signed or unsigned?
230  float_pkg
231  process( all ) -- compiler cannot infer the sensitivity list
233  Vhpi_user.h requires enum types contents update/completion
234  Backward incompatibility for std_logic_textio selected names
235  Error in name of property of foreignf class
236  Wrong case for specName property of blockConfig class
237  Representation of negative time values with vhpiTimeT
238  What is vhpiBootstrapFctT for in vhpi_user.h?
242  Simple typo in D4.2
243  PSL-specific reserved words
244  Ballot response: Make VHPI optional
245  References in both normative section and bibliography
246  Typos
247  Use of "bit" vs. "element"
248  Wrong case for TRUE

Verify resolved issues before D4.2
184  Condition operator ?? is not predefined for STD_ULOGIC
185  Definitions for unconstrained and fully constrained recor...
186  Missing single quote in CHARACTER type declaration
187  Missing closing parenthesis in "<" function declaration
190  logical operator return array index ranges not consistent
191  Condition operator should be implicitly applied to guard ...
192  Subtype problems for out-mode signal parameters
193  Sensitivity of concurrent procedure call with out-mode si...
194  Missing rule for profile conformance of generic subprograms
195  Missing rule for base type of an external name
196  Path name attribute strings include loop labels, but loop...
197  Missing semicolon in rule for library clause in Annex A
198  Array type definition syntax not updated in Annex A
199  Semicolons missing in productions for force assignments
200  Spurious semicolons in grammar for interface elements
201  New syntax for bit-string literals missing from Annex A
202  Superceded reference to "generation scheme"
203  Incorrect cross reference for string representation for T...
204  Reference to replacement characters not deleted
205  Glossary entry for "change" not updated

Deferred Issues:

17    add_carry in numeric_std as well as fixed/floating packages
58    Wording problem with operator overloading
157   to_string in package standard
206   What exactly does FINISH do? Can it be used?
207   Input values for STOP
218   Permitted access into encrypted code unclear
239   IR2130: Ability to overload the assignment operator := would be 
useful
240   IR2132: Method to allow functions that return arrays to have 
knowledge of the array bounds







-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Wed Jul 16 18:35:14 2008

This archive was generated by hypermail 2.1.8 : Wed Jul 16 2008 - 18:35:17 PDT