Re: [sv-ac] Example shown in LRM contradicts local variable restriction

Hi Doron:

I agree with you that the example from 16.8.2 is correct according 
to the rules for local variable formal arguments.

The last paragraph of 16.8.2 tries to point out that the "old style"
exists and is described in 16.10.

It was not intended for the "old style" from 16.10 to make the new
style in 16.8.2 illegal -- that would be pointless.

However, there may still exist text in 16.10 that is confusing when
considered alongside the "new style" of 16.8.2.  Given the state
of the LRM, clarification will have to wait, but a mantis could be
entered.

J.H.

> X-eda.org-MailScanner-Watermark: 1231328650.0892@w1X8rAHTXWid6SPkmirnpQ
> X-Authentication-Warning: server.eda.org: majordom set sender to owner-sv-ac@eda.org using -f
> X-eda.org-MailScanner-Watermark: 1231328587.0755@4GK7cdduiATcapDHNc4LpA
> X-ExtLoop1: 1
> X-IronPort-AV: E=Sophos;i="4.36,307,1228118400"; 
>    d="scan'208,217";a="478080595"
> From: "Bustan, Doron" <doron.bustan@intel.com>
> Date: Wed, 31 Dec 2008 13:42:59 +0200
> Thread-Topic: [sv-ac] Example shown in LRM contradicts local variable
>  restriction
> Thread-Index: Aclp2QqnL5F4G1NRTtCLa5yEgZI1bQBYjeGAAAAvESA=
> Accept-Language: en-US
> Content-Language: en-US
> X-MS-Has-Attach: 
> X-MS-TNEF-Correlator: 
> acceptlanguage: en-US
> X-eda.org-MailScanner: Found to be clean, Found to be clean
> X-Spam-Status: No, No
> Sender: owner-sv-ac@eda.org
> X-eda.org-MailScanner-Information: Please contact the ISP for more information
> X-MailScanner-ID: mBVBi9CL005723
> X-eda.org-MailScanner-From: owner-sv-ac@server.eda.org
> X-OriginalArrivalTime: 31 Dec 2008 11:45:47.0624 (UTC) FILETIME=[52641E80:01C96B3D]
> 
> 
> --_000_C069EF73131DDB4788AA7BC1F10A819125054381hasmsx501gercor_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
> 
> I have read it,
> 
> The text is coming from 1549. As far as I remember the restriction on typed=
>  local formal argument was removed when local input/output/inout were intro=
> duced (1667). One can see that in annex F. So I think that the example is c=
> orrect and the text should have been removed.
> John, can you comment about that?
> 
> Doron
> 
> 
> ________________________________
> From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Beh=
> alf Of Bresticker, Shalom
> Sent: Wednesday, December 31, 2008 1:33 PM
> To: Surya Pratik Saha; sv-ac@server.eda.org
> Subject: RE: [sv-ac] Example shown in LRM contradicts local variable restri=
> ction
> 
> In Draft 8-preliminary, the example is on page 323 (PDF file p. 356) and th=
> e text is on page 348 (PDF page 381).
> 
> Shalom
> 
> ________________________________
> From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Beh=
> alf Of Surya Pratik Saha
> Sent: Monday, December 29, 2008 7:11 PM
> To: sv-ac@server.eda.org
> Subject: [sv-ac] Example shown in LRM contradicts local variable restriction
> Hi,
> I did not get any answer of last mail. So I am resending it:
> 
> In SV 2009 draft LRM, there is an example:
> sequence sub_seq2(local inout int lv);
> (a ##1 !a, lv +=3D data_in)
> ##1 !b[*0:$] ##1 b && (data_out =3D=3D lv);
> endsequence
> sequence seq2;
> int v1;
> (c, v1 =3D data)
> ##1 sub_seq2(v1) // lv is initialized by assigning it the value of v1;
> // when the instance sub_seq2(v1) matches, v1 is
> // assigned the value of lv
> ##1 (do1 =3D=3D v1);
> endsequence
> 
> And later it is mentioned:
> It can be useful to assign a value to a local variable within an instance o=
> f a named sequence and reference the
> local variable in the instantiating context at or after the completion of a=
>  match of the instance. This capability
> is supported under the following conditions:
> - The local variable shall be declared outside the named sequence, and its =
> scope shall include both the
> instance of the named sequence and the desired reference in the instantiati=
> ng context.
> - The local variable shall be passed as an entire actual argument in the li=
> st of arguments of the
> instance of the named sequence.
> - The corresponding formal argument shall be untyped.
> 
> Whereas, in the example corresponding formal argument 'lv' is not untyped f=
> or local variable 'v1'. Am I missing anything?
> 
> 
> --
> 
> Regards
> 
> Surya
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner<http://www.mailscanner.info/>, and is
> believed to be clean. --
> 
> This email was Anti Virus checked by Astaro Security Gateway. http://www.as=
> taro.com
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner<http://www.mailscanner.info/>, and is
> believed to be clean. --
> 
> This email was Anti Virus checked by Astaro Security Gateway. http://www.as=
> taro.com
> 
> ---------------------------------------------------------------------
> 
> 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.
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner<http://www.mailscanner.info/>, and is
> believed to be clean.
> ---------------------------------------------------------------------
> 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.
> 
> --=20
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 

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