From: Steven Sharp (sharp@cadence.com)
Date: Fri Jan 28 2000 - 12:47:01 PST
Draft 4 page 153, section 10.2.3, new paragraphs after paragraph 1
WAS:
PROPOSED IS:
Variables declared in static tasks shall retain their values between
invocations. They shall be initialized to the default initialization
value as described in section 3.2.2. Variables declared in automatic tasks
shall be initialized to the default initialization value whenever
execution enters their scope.
Because variables declared in automatic tasks are deallocated at the end
of the task invocation, they shall not be used in certain constructs
that might refer to them after that point.
-- They shall not be assigned values using non-blocking assignments
or procedural continuous assignments.
-- They shall not be referenced by procedural continuous assignments
or procedural force statements.
-- They shall not be referenced in intra-assignment event controls
of non-blocking assignments.
-- They shall not be traced with system tasks such as $monitor and
$dumpvars.
PROPOSED CHANGE:
This change was submitted for Draft 4, but somehow failed to get
included. Now modified to replace references to regs with references
to variables.
Describe the initialization and constraints on automatic variables as
approved by the BTF. This text could be put at the end of section
10.2.1 instead.
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:54:11 PDT
and
sponsored by Boyd Technology, Inc.