Hi
Surya,
Sure,
when you see any issue that looks like an error or that
requires a clarification, feel free to file a Mantis item if you do not
get a
satisfactory explanation from the email forum.
Regards,
Dmitry
Hi Dmitry,
If that is the case, should I file a Mantis against that. I got the
mantis
account from Neil, so it will not be a problem for me now.
Regards
Surya
-------- Original Message --------
Subject: Re:[sv-ac] Restriction inside checker construct
From: Korchemny, Dmitry <dmitry.korchemny@intel.com>
To: Seligman, Erik <erik.seligman@intel.com>,
Surya Pratik Saha <spsaha@cal.interrasystems.com>,
sv-ac@eda.org
<sv-ac@eda.org>
Date: Tuesday, January 06, 2009 6:12:55 PM
Hi
Surya, Erik,
I
think that the intention is that the checker cannot refer
hierarchically to the data defined in automatic functions, etc.
I
don’t think that automatic tasks and functions should be
referenced here since 13.3.1 Static and automatic tasks explicitly
states that
“Automatic task items cannot be accessed by hierarchical
references”, and 13.4.2 Static and automatic functions states the same
thing about the automatic functions.
The
whole text is indeed confusing, and probably should better
be dropped altogether.
Dmitry
I
think this may be leftover text from an earlier version where we
were considering allowing checkers in tasks and functions.
Dmitry,
do you have further comments?
Hi,
I have already sent the mail some days back, but did not get any reply,
maybe
because of holiday. So I am resending it.
It is mentioned in the SV 2009 draft LRM:
The following elements from the scope enclosing the checker
declaration
shall not be referenced in a checker:
— Automatic variables and members or elements of dynamic variables.
This
includes dynamically sized variables and data in automatic tasks,
functions, or
blocks.
— Elements of fork...join, fork...join_any, or fork...join_none blocks.
The text is little bit confusing. The checker declaration is not
possible
inside a task/function scope. So referring a variable from a
task/function
requires hierarchical reference. But any variable can not be
hierarchically
referred from an automatic task/function. So why it is mentioned
separately
here. Or does it signify something else. It will better to understand
if some
proper example is shown with that text.
--
Regards
Surya
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.