ISAC: Proposed agenda for ISAC meeting 22 May 2008

Next meeting: Thursday, May 22, 2008, 8 pm Pacific Daylight time.
             (Friday, May 23, 2008, 3 am GMT)

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

Here is my categorization. Admittedly, it is rather arbitrary,
but it is a starting point.

Easy Bugzilla Issues are simple typos or
misstatements whose solution is fairly obvious.
My hope is that you will read these issues before the meeting
and will raise any concerns at the meeting. Otherwise, these should
basically be approved by default.

Medium issues vary in complexity, but all require some word smithing.

Non-trivial issues require substantive decisions.

1. Easy Bugzilla Issues:

208 D4.2 simple typos
210 ?? for STD_ULOGIC still listed in table in 9.2.9
216  Clause title on VHDL-87 is out of date.
224  In glossary, some references are out of order.
227  glossary entry for expanded name has incorrect reference 

2. Medium Bugilla Issues;

209 Line numbers don't align
211 Confusing rules for object aliases.
212 Inconsistent treatment for PSL declarations
214 Semantics of some READ procedures are not complete
215 Problem with deallocation of lines in textio.
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...
225 Glossary description of complete context is no longer cor...
226 glossary entry for "design unit" is no longer correct
228 Glossary entry for floating-point type is incorrect
229 Is type vhpiIntT signed or unsigned?
230 float_pkg

3. Non-trivial Bugzilla Issues:

213 Can a force signal assignment update ports of mode IN?
217 Confusing/contradictory requirements for modport objects
218 Permitted access into encrypted code unclear
219 What directives can appear in encrypted source text and ...
231 process( all ) -- compiler cannot infer the sensitivity list

3. Deferred Issues:

206 What exactly does FINISH do? Can it be used?
207 Input values for STOP

IR 2130 Ability to overload the assignment operator := would be useful




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.