RE: [sv-ac] 928

All,

I also like that.  

lisa

-----Original Message-----
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of John
Havlicek
Sent: Tuesday, January 30, 2007 9:37 AM
To: Surrendra.Dudani@synopsys.com
Cc: sv-ac@eda.org
Subject: Re: [sv-ac] 928

All:

What about Surrendra's point that event expressions are not
included under expressions?

If you look at purpose number 3 in 928, it says

   tf_port list was replaced by sequence_port_list and
   property_port_list to fix the issue that tf_port_list
   does not allow default values assignment other than 
   expression.  The new definition allows for initialization
   of all args in the definition.
   
I like Surrendra's suggestion of using property_actual_arg (resp.,
sequence_actual_arg) for the default assignments in a
property_port_list (resp., sequence_port_list).

J.H.

> X-Authentication-Warning: server.eda-stds.org: majordom set sender to
owner-sv-ac@eda.org using -f
> X-MimeOLE: Produced By Microsoft Exchange V6.5
> Content-class: urn:content-classes:message
> Date: Fri, 26 Jan 2007 07:53:13 -0800
> Thread-Topic: [sv-ac] 928
> Thread-Index: AcdAwOe7Vlfpkh8hQz6eKRgSBv5zmwAAlkhQACRieVAAAlMsKAAA71Tg
> From: "Surrendra Dudani" <Surrendra.Dudani@synopsys.com>
> X-OriginalArrivalTime: 26 Jan 2007 15:53:14.0916 (UTC)
FILETIME=[16D75640:01C74162]
> X-eda.org-MailScanner: Found to be clean, Found to be clean
> X-Spam-Status: No, No
> X-MIME-Autoconverted: from quoted-printable to 8bit by
server.eda-stds.org id l0QFrUwE021594
> Sender: owner-sv-ac@eda.org
> X-eda.org-MailScanner-Information: Please contact the ISP for more
information
> X-eda.org-MailScanner-From: owner-sv-ac@server.eda.org
> 
> Hi Bassam,
> expr does not include event_expr, so one is not able to specify event
> expression as default argument.
> Surrendra
> 
> -----Original Message-----
> From: Bassam Tabbara [mailto:bassamt@synopsys.COM] 
> Sent: Friday, January 26, 2007 10:25 AM
> To: Surrendra.Dudani@synopsys.COM; sv-ac@eda.org
> Subject: Re: [sv-ac] 928
> 
> Hi Surrendra,
> 
> Right now it is much like tf_port_list's default init. Unless it is
> missing something in my opinion this form is better.
> 
> THX. 
> -Bassam
> 
> -----Original Message-----
> From: owner-sv-ac@eda.org <owner-sv-ac@eda.org>
> To: sv-ac@eda.org <sv-ac@eda.org>
> Sent: Fri Jan 26 06:25:07 2007
> Subject: RE: [sv-ac] 928
> 
> Hi Lisa/Bassam,
> Thanks for the answers.
> Yes, you are right about the (1). sequence_instance is indeed included
> in event-expresion.
> For (2),
> Would it not be consistent to allow actual arg as the default, as
shown
> below?
>  
> 
> property_port_item ::=
> { attribute_instance }
> property_formal_type
> port_identifier {variable_dimension} [=property_actual_arg] 
> 
> sequence_port_item ::=
> { attribute_instance }
> sequence_formal_type
> port_identifier {variable_dimension} [=sequence_actual_arg] 
> 
> Surrendra
> 
> ________________________________
> 
> From: Lisa Piper [mailto:piper@cadence.com]
> Sent: Thursday, January 25, 2007 4:14 PM
> To: Surrendra Dudani; sv-ac@eda.org
> Subject: RE: [sv-ac] 928
> 
> 
> 
> Hi Surrendra,
> 
>  
> 
> I have tried to answer the questions, though I'm not sure I understand
> the second question.
> 
>  
> 
> Lisa Piper
> 
>  
> 
> ________________________________
> 
> From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
> Surrendra Dudani
> Sent: Thursday, January 25, 2007 3:39 PM
> To: sv-ac@eda.org
> Subject: [sv-ac] 928
> 
>  
> 
> Hi John/Dmitry, 
> I was looking at mantis item 928 which was passed last year, and need
> the following clarifications: 
> 1) Unlike property actual argument, 
> property_actual_arg::= 
>         property_instance 
>         | sequence_actual_arg 
> 
> sequence actual argument does not include sequence_instance 
> sequence_actual_arg ::= 
>         event_expression 
> 
> [Lisa Piper >>>] if you look at the definition of event_expression, it
> already includes a sequence instance.
> 
> 2) The default argument for either property or sequence declaration is
> expression rather than actual sequence/property expression
> 
> property_port_item ::= 
> { attribute_instance } 
> property_formal_type 
> port_identifier {variable_dimension} [=expression] 
> 
> sequence_port_item ::= 
> { attribute_instance } 
> sequence_formal_type 
> port_identifier {variable_dimension} [=expression] 
> 
> [Lisa Piper >>>] If I understand the question correctly, you are
> questioning how an "expression" can be a default value when the
argument
> that is passed is a sequence or property.  I think the intent is:
> 
>             define property ( reg x=<expr> ) .....  which says that
the
> default value for argument x is <expr>
> 
> Currently you cannot have a property or sequence argument type since
> these are not yet defined as a sequence_formal_types, and in fact,
while
> they can be passed untyped, you can only pass an instance.  I think
the
> 1549 proposal that suggests adding these will need to address whether
it
> makes sense to be able to define an initializer.
> 
> Thanks 
> Surrendra 
> **************************************** 
> Surrendra A. Dudani 
> Synopsys, Inc. 
> 377 Simarano Drive, Suite 300 
> Marlboro, MA 01752 
> 
> Tel:   508-263-8072 
> Fax:   508-263-8123 
> email: Surrendra.Dudani@synopsys.com  
> **************************************** 
> 
> 
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner <http://www.mailscanner.info/> , and
is
> 
> believed to be clean. 
> 
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner <http://www.mailscanner.info/> , and
is
> 
> believed to be clean. 
> 
> -- 
> 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.


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