MINUTES of ISAC meeting held via telecom on 13 March 2008

Present: Larry Soule, Chuck Swart, Lance Thompson

Absent: Peter Ashenden, Jim Lewis, Ajay Verikat

Next meeting: Thursday, March 20, 2008, 8 pm Pacific Daylight time.
              (Friday, March 21, 2008, 3 am GMT)

NOTE: Since attendance was low, all decisions are subject to review.
If you disagree with any decisions, let me know and we'll discuss them
at the next meeting.

TOPIC: IR 2126 Concatenation ambiguity

There was general agreement about the direction of the analysis.
We want to close this as soon as we can, so everyone needs to
review version 3 and vote or send in their issues.

ACTION: All to vote by March 20.

TOPIC: Bugzilla maintenance:

Chuck will update Bugzilla so that not everyone can change STATUS
fields. The current, wide-open situation could allow someone to close
an issue without proper review.

TOPIC: Bugzilla 192 Subtype problems for out-mode signal parameters,
and 193 Sensitivity of concurrent procedure call with out-mode signal
parameter

It seems that the best solution to both of these problems is to
disallow reading of OUT mode signal parameters, while allowing
reading of OUT mode ports and variables. This seems to best meet the
original FT requirement, remains backward compatible, and avoids the
serious issues raised by these two issues.

The original FT requirement was to allow reading of OUT mode ports.
At a face-to-face meeting it was agreed to extend this capability to
OUT mode variables (Ada allows this) and signal parameters. No one could
remember specific reasons, except for uniformity, to allow this for
signal parameters. Anyone remember more details?

ACTION: All to consider this proposed solution and decide if this is
the best decision.

TOPIC: IR 2123 Process resumption and callbacks and IR 2124 Ordering of
process execution and callbacks

Chuck distributed several emails from VHPI folks about these issues.
We suspended discussion about final resolution until Peter can participate.

ACTION: All to review the emails. We'll try to resolve at the next meeting.

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

The suggestion to standardize at least some values to STOP/FINISH is
an enhancement request. If it is resolved, the time for resolution is
longer than the time frame for the next VHDL version. Therefore, it was
decided not to attempt to work this into the imminent LRM revision.

TOPIC: IEEE editorial/stylistic changes to LRM. 

Lance asked if we really need to make these changes. Chuck remarked that
Dennis Brophy, a REV CON member, stated that these style "standards" are only
IEEE recommendations and that the IEEE can't force document writers to follow them. As LRM writer, Peter is the person who knows the most about what's really
going on, and he will be asked to report on this at the next meeting.

ACTION: This will be discussed at the next meeting.

NOTE: We have a target goal of next meeting to reach final (ISAC) resolution
on all VHDL-200X issues. Some of the open issues require VASG approval, but
in any event, we are close to final decisions about final language features
for the next version.