RE: [sv-ec] Question on Mantis 3293

Arturo,

Thanks. I'll make these changes as part of entering the Mantis item into
draft 3.

Stu
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland

Sutherland HDL, Inc.

stuart@sutherland-hdl.com

503-692-0898
www.sutherland-hdl.com

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Arturo
Salz
Sent: Friday, November 04, 2011 11:49 AM
To: Stuart Sutherland; Mehdi.Mohtashemi@synopsys.COM
Cc: neil.korpusik@oracle.com; sv-ec@eda.org
Subject: RE: [sv-ec] Question on Mantis 3293

Stu,

Items 2 and 3 are indeed typos (the result of an earlier edit). There should
be one semicolon at the end of both declarations: task and function, as
shown:

function int $cast( singular dest_var, singular source_exp );

or

task $cast( singular dest_var, singular source_exp );

I don't know how to a bug note once the mantis is resolved. If either of you
know please let me know and I'll add the note.

As for item 1, I believe prototype is better. I recommend the change as an
editorial improvement by you (the editor).

                Arturo

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Stuart
Sutherland
Sent: Friday, November 04, 2011 9:42 AM
To: Mehdi.Mohtashemi@synopsys.COM
Cc: neil.korpusik@oracle.com; sv-ec@eda.org
Subject: [sv-ec] Question on Mantis 3293

Mehdi,

I have three quick questions regarding the proposal for Mantis 3293:

1. Should "The syntax for $cast is." be "The prototype for $cast is."?
Other proposals have made a similar change.

2. Should there be two semicolons at the end of the function form of
the $cast prototype?

3. Should a semicolon at the end of the task form of the $cast
prototype?

If any corrections are required, please let me know by responding to this
e-mail and by adding a bug note with those changes. I will need an answer
today in order to incorporate any changes into draft 3.

Stu
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland

Sutherland HDL, Inc.

stuart@sutherland-hdl.com

503-692-0898
www.sutherland-hdl.com

-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 
-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> 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.